RE: CIFS and the krb5 PRF
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: CIFS and the krb5 PRF



What about adding a flag argument to GSS_Pseudo_random(), thus we can
allow implementations to *optionally* expose the raw session key via the
PRF. I am saying so assuming folks genuinely need to support a way to
interop with existing applications that expose the direct Kerberos key
today, Kerb-TLS, to think of it, is one of them.

-- Larry


-----Original Message-----
From: kitten-bounces at lists.ietf.org
[mailto:kitten-bounces at lists.ietf.org] On Behalf Of Andrew Bartlett
Sent: Monday, June 27, 2005 3:37 AM
To: Jeffrey Altman
Cc: kitten at ietf.org; Sam Hartman
Subject: Re: CIFS and the krb5 PRF

On Mon, 2005-06-27 at 05:27 -0400, Jeffrey Altman wrote: 
> Andrew Bartlett wrote:
> 
> > Given the strongly held views of represented here that Samba4 (in
> > particular) should not be locked into a particular Kerberos/GSSAPI
> > implementation, where should I address discussion about the changes
that
> > Samba4 requires?
> > 
> > I have already made a number of experimental modifications to
Heimdal
> > kerberos (a copy of which we will ship built into Samba4 for initial
> > release).  While I already get some good feedback from Love, I know
> > others have views.  
> > 
> > The 'CIFS Session key' export is just one of these required
extensions -
> > we also need to change the GSS_Wrap arguments to support AEAD, and
> > closer control over the underlying Kerberos behaviour.
> > 
> > Andrew Bartlett
> 
> Discussions of proprietary mechanism extensions for Kerberos 5 such as
> access to the Kerberos 5 ticket (or ticket parts) that you wish to be
> adopted by both Heimdal and MIT Kerberos should take place on the
> krbdev at mit.edu mailing list. &#-1;&#-1; 
>
> The same is true for anything other
> change that would be incompatible with implementations of GSS API
> version 2 update 1.
> 
> Discussions that are appropriate for the Kitten list are any changes
> this working group should consider for GSS API version 3.

Well, I certainly would like to see GSS API version 3 being flexible
enough to provide the facilities that Samba4 requires.  That would seem
to be a desirable outcome.  Clearly not all the things Samba4 requires,
fit into that category, but I think some do.

I'll continue hacking my way though GSSAPI as I move forward, let me
know if you want to hear about what things I'm finding.

Andrew Bartlett

-- 
Andrew Bartlett
http://samba.org/~abartlet/
Samba Developer, SuSE Labs, Novell Inc.        http://suse.de
Authentication Developer, Samba Team           http://samba.org
Student Network Administrator, Hawker College  http://hawkerc.net

_______________________________________________
Kitten mailing list
Kitten at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.