Encrypting krb_rced messages in GSSAPI tokens

[Nicolas.Williams@ubsw.com]

Doh. You can't allocate the keys in the auth context constructor. Yeah, you either have to split up mk_req or put in a callback interface.

Nico
--  

> -----Original Message-----
> From: Williams, Nicolas 
> Sent: Monday, April 29, 2002 5:24 PM
> To: 'Sam Hartman'
> Cc: krbdev at mit.edu
> Subject: RE: Encrypting krb_rced messages in GSSAPI tokens
> 
> 
> 
> Yeah, you could make the auth context constructor generate 
> the subkey. Then the app could use that key before calling 
> mk_req_extended(). It's just as well, and probably easier 
> than the callback. Easier should win, right?
> 
> Nico
> --  
> 
> > -----Original Message-----
> > From: Sam Hartman [mailto:hartmans at mit.edu]
> > Sent: Monday, April 29, 2002 5:20 PM
> > To: Williams, Nicolas
> > Cc: krbdev at mit.edu
> > Subject: Re: Encrypting krb_rced messages in GSSAPI tokens
> > 
> > 
> > >>>>> "Nicolas" == Nicolas Williams 
> > <Nicolas.Williams at ubsw.com> writes:
> > 
> >     Nicolas> Suggestion: change mk_req_extended() (or make 
> a new API)
> >     Nicolas> that takes a callback function pointer and 
> make it so the
> >     Nicolas> callback function gets called with the ticket key and
> >     Nicolas> subkey blocks; the callback function should return data
> >     Nicolas> for use in the checksum field.
> > 
> > That's certainly one way to handle it.  I was actually thinking of
> > splitting out the key setup into a different function.  I 
> think I may
> > like the callback method better.
> > 
> > 
> 

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.