On Sun, Nov 18, 2001 at 11:18:39PM -0000, Mayers, Philip J wrote: > Forget it - I got it now. > > It seems like a curious (read: awkward) format though - is there any reason > it isn't simply the KDC_REP (with the encrypted part unencrypted, of > course)?
As the client fetches individual service tickets these can be added to the ccache... But a ccache should be associated with but one user principal. A set of KDC_REPs would not do... That said, an unencrypted KRB_CRED would do. And it would make it trivial to serialize a ccache (and area of MIT krb5 code that needs work). Cheers, Nico > Don't even get me started on the Keytab format... :o) > > Cheers, > Phil > > -----Original Message----- > From: Mayers, Philip J > To: '[EMAIL PROTECTED]' > Sent: 18/11/2001 18:54 > Subject: Ccache format > > I'm writing an MIT-compatible credcache implementation, and the README > in > the krb5-1.2.2 sources appears to be wrong. I've gotten this, but I'm > not > sure about the is_skey, ticket_flags, and two tickets of data. Could > someone > help me out please? > > Cheers, > Phil -- -DISCLAIMER: an automatically appended disclaimer may follow. By posting- -to a public e-mail mailing list I hereby grant permission to distribute- -and copy this message.- 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.
