[19731] in Kerberos_V5_Development
Re: Development environment setup
daemon@ATHENA.MIT.EDU (Idan Freiberg)
Mon Feb 26 11:36:44 2018
MIME-Version: 1.0
In-Reply-To: <jlgefl7k94m.fsf@redhat.com>
From: Idan Freiberg <speidy@gmail.com>
Date: Mon, 26 Feb 2018 16:31:11 +0000
Message-ID: <CAOWMy3nqc6j5gC5_JO1nfRB6890SQQ1M3Y3woHMbsDKbNC7EHw@mail.gmail.com>
To: Robbie Harwood <rharwood@redhat.com>
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="utf-8"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
Robbie, I have an experience with both of the apis.
U2U RFC is already implemented by MS Both in Kerberos client and KDC.
I want to make MIT Kerberos interoperable with it as well.
בתאריך יום ב׳, 26 בפבר׳ 2018 ב-18:28 מאת Robbie Harwood <rharwood@redhat.com
>:
> Idan Freiberg <speidy@gmail.com> writes:
>
> > I’m planning to work on Kerberos u2u support. I would like to have
> > you advice on what is the best env setup I should do for development.
> >
> > I want the code to be compatible with MS KDC as well.
> >
> > Should I code against Samba KDC first? The addition is mainly in the
> > gssapi area I think.
>
> Samba uses MIT (or Heimdal, depending on where you get it and how you
> build it) these days, and I think the debuggability you'll get out of
> those will be a lot higher than from Microsoft's.
>
> What do you mean by "addition"? Microsoft's KDC isn't open source, so I
> don't know how you could add things to it - this means protocol changes
> are going to be difficult. Also, it doesn't support the GSSAPI (there
> is some measure of compatibility between GSSAPI and SSPI on the wire,
> but the API is not identitcal).
>
> Thanks,
> --Robbie
>
--
Idan Freiberg
PGP FP: 8108 7EC9 806E 4980 75F2 72B3 8AD3 2D04 337B 1F18
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
