misc/113266: Missing handling of mech_type in gss_init_sec_context being GSS_C_NO_OID

[Eirik A. Nygaard]

>Number:         113266
>Category:       misc
>Synopsis:       Missing handling of mech_type in gss_init_sec_context being GSS_C_NO_OID
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 02 20:30:06 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Eirik A. Nygaard
>Release:        7.0-CURRENT
>Organization:
>Environment:
FreeBSD eirik 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue May  8 12:33:42 CEST 2007     eirik@:/usr/obj/home/eirik/FreeBSD/src/sys/EIRIK  i386

>Description:
When passing GSS_C_NO_OID to gss_init_sec_context as the mech_type argument libgssapi will segfault in _gss_oid_equal(gss_utils.c:39). The manpage states that:
     mech_type     Object ID of desired mechanism. Supply GSS_C_NO_OID to
                   obtain an implementation specific default

So sending in GSS_C_NO_OID as mech_type should be allowed.
>How-To-Repeat:
Issue a gss_init_sec_context() call with the mech_type argument being GSS_C_NO_OID. Then wait for the segfault.
>Fix:
Patch can be found at: http://www.pvv.ntnu.no/~eirikald/patches/gssapi_mech_type_NO_OID.patch

>Release-Note:
>Audit-Trail:
>Unformatted: