Better support for "non-standard" GSS mechs
authorNicolas Williams <nico@twosigma.com>
Fri, 17 Apr 2020 03:53:22 +0000 (22:53 -0500)
committerNico Williams <nico@cryptonector.com>
Fri, 17 Apr 2020 19:37:39 +0000 (14:37 -0500)
commit92c288994ad2ecc4e6842bf74dabd0c1c21ca28f
treeafcfd700433a564f8b8403adfbb47c69de58f380
parent4199118c7670ebe8604b4b839850fa7e08a4077f
Better support for "non-standard" GSS mechs

If an initial security context token doesn't have a standard header per
RFC2743 then try all mechanisms until one succeeds or all fail.

We still try to guess NTLMSSP, raw Kerberos, and SPNEGO, from tasting
the initial security context token.
lib/gssapi/krb5/accept_sec_context.c
lib/gssapi/mech/gss_accept_sec_context.c
lib/gssapi/ntlm/accept_sec_context.c
lib/gssapi/ntlm/init_sec_context.c