[33614] in Kerberos
Re: threading best practices?
daemon@ATHENA.MIT.EDU (Nico Williams)
Fri Jul 22 15:51:34 2011
MIME-Version: 1.0
In-Reply-To: <4E2904B4.1040406@d6.com>
Date: Fri, 22 Jul 2011 14:51:27 -0500
Message-ID: <CAK3OfOjKY-VQ3josPtBF2iTW4zibLZrYqgTpbXffWAmK26QW0w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Chris Hecker <checker@d6.com>
Cc: "kerberos@mit.edu" <kerberos@mit.edu>
Content-Type: text/plain; charset="utf-8"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On Fri, Jul 22, 2011 at 12:03 AM, Chris Hecker <checker@d6.com> wrote:>> I don't think any u2u stuff is stored in a krb5_context. Can you be>> more specific about what you're seeing here?>> I'm not seeing anything yet, since I'm still trying to figure out how> I'm going to do this by playing around with the sample apps. I think> I'm getting confused between krb5_context and krb5_auth_context, I'm not> totally clear on how they relate or depend on one another...
krb5_context is just a caller context that must be passed topractically all krb5 APIs.
krb5_auth_context is the raw krb5 API equivalent of GSS'gss_sec_context_t -- it represents an authenticated channel betweentwo end-points.
> Okay, so if I krb5_get_credentials on the KDC thread, I can then use> them in the main thread with a different context...
Yes, pretty much.
Nico--
________________________________________________Kerberos mailing list Kerberos@mit.eduhttps://mailman.mit.edu/mailman/listinfo/kerberos
