[11491] in Kerberos-V5-bugs

home help back first fref pref prev next nref lref last post

[krbdev.mit.edu #6696] gss_accept_sec_context doesn't produce error

daemon@ATHENA.MIT.EDU (Arlene Berry" via RT)
Mon Apr 5 19:54:28 2010

Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: ""Arlene Berry" via RT" <rt-comment@krbdev.MIT.EDU>
In-Reply-To: <rt-6696@krbdev.mit.edu>
Message-ID: <rt-6696-32701.0.906650177287318@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6696'":;"'AdminCc of krbdev.mit.edu Ticket #6696'":;@MIT.EDU
Date: Mon,  5 Apr 2010 19:54:26 -0400 (EDT)
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu

The mechglue for gss_accept_sec_context suppresses error tokens which
means that an initiator who is waiting for a response after receiving
GSS_S_CONTINUE-_NEEDED is never notified that there's a problem.  It
appears the code has been this way ever since the mechglue was
introduced.  This fixes it for me:

 

Index: g_accept_sec_context.c

===================================================================

--- g_accept_sec_context.c         (revision 42878)

+++ g_accept_sec_context.c      (working copy)

@@ -385,9 +385,6 @@

                free(union_ctx_id);

     }

 

-    if (output_token->length)

-              (void) gss_release_buffer(&temp_minor_status,
output_token);

-

     if (src_name)

                *src_name = GSS_C_NO_NAME;

 


_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs

home help back first fref pref prev next nref lref last post