home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Thu, 09 Oct 2014 11:12:01 +0000 From: "Xie, Hugh" <hugh.xie@bankofamerica.com> In-reply-to: <5435FCA4.9030709@mit.edu> To: "'Greg Hudson'" <ghudson@mit.edu>, "'Kerberos@mit.edu'" <Kerberos@mit.edu> Message-id: <7E270C3427928E499F189C5636C52CDC45B9FDD8@smtp_mail.bankofamerica.com> MIME-version: 1.0 Content-language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kerberos-bounces@mit.edu Perhaps this is a bug. Gss_init_sec_context did return GSS_S_COMPLETE for me. -----Original Message----- From: Greg Hudson [ghudson@mit.edu<mailto:ghudson@mit.edu>] Sent: Wednesday, October 08, 2014 11:10 PM Eastern Standard Time To: Xie, Hugh; Kerberos@mit.edu Subject: Re: Not getting delegation credential from gss_accept_sec_context() On 10/08/2014 05:45 PM, Xie, Hugh wrote: > My mistake. The error is from * gss_inquire_context(&min_stat, state->context, &gssuser, NULL, NULL, NULL, NULL, NULL, NULL);* post call to * gss_init_sec_context*. Can I still call this function post gss_init_sec_context with delegate handle? Our implementation requires the context argument of gss_inquire_context to be an established context, although this isn't required by RFC 2743 or RFC 2744. I will file an issue. For the moment, don't inquire the context until gss_init_sec_context returns GSS_S_COMPLETE. ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. ________________________________________________ Kerberos mailing list Kerberos@mit.edu https://mailman.mit.edu/mailman/listinfo/kerberos
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |