s3-gse: Use the session key type, not the lucid context to set NEW_SPNEGO
authorAndrew Bartlett <abartlet@samba.org>
Tue, 14 Feb 2012 07:29:54 +0000 (18:29 +1100)
committerStefan Metzmacher <metze@samba.org>
Thu, 16 Feb 2012 14:18:42 +0000 (15:18 +0100)
commit5c9b6db68e0f535ed2b42bbfee310b7cebf65ca4
tree4cdda382b5e50b351311c036d04cb5fa26b4c1fa
parent1d0684c8452ddaec3ab3f715382503c87b0ec534
s3-gse: Use the session key type, not the lucid context to set NEW_SPNEGO

Using gss_krb5_export_lucid_sec_context() is a problem with MIT krb5, as
it (reasonably, I suppose) invalidates the gssapi context on which it
is called.  Instead, we look to the type of session key which is
negotiated, and see if it not AES (or newer).

If we negotiated AES or newer, then we set GENSEC_FEATURE_NEW_SPENGO
so that we know to generate valid mechListMic values in SPNEGO.

Andrew Bartlett

Signed-off-by: Stefan Metzmacher <metze@samba.org>
source3/librpc/crypto/gse.c