Re: Comments on draft-ietf-kitten-krb5-gssapi-prf-03.txt

On Tue, May 24, 2005 at 01:54:57AM +0200, Martin Rex wrote:
> Nicolas Williams wrote:
> > 
> > On Tue, May 24, 2005 at 12:43:37AM +0200, Martin Rex wrote:
> > > As with a similar discussion on krb-ietf list how a KDC cert should
> > > be verified in PKINIT, we should not ignore the fact that the affected
> > > spec (here) is going to be normative for both, the gssapi mechanism
> > > implementor and the application gssapi caller, and those two
> > > will have an entirely different background and needs.
> > > 
> > > We should add a reference to the document draft-eastlake-randomness2-10.txt
> > > that is sitting on the Editor's queue:
> > 
> > With respect to what?  The input to the PRF?
> 
> You got me, I'm not following my own advice.
> 
> This reference should be guidance for gssapi mechanism implementors
> that provide PRF output based on the cryptographic session key.

There's already plenty of text on what properties a mechanism's
GSS_Pseudo_random() must have.  Or do you see anything missing?

And as for randomness, that is a core consideration for the mechanisms
and totally out of scope here as GSS_Pseudo_random() can only use keys
already exchanged by the mechanism during security context
establishment and already considered, by the mechanism, good enough for
per-message protection services.

Nico
-- 

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