r20107: don't segfault when the server didn't send a supportedMech in a negTokenTarg
commit5af5488593991ab4a2a8e17d38501ad9ec539020
authorStefan Metzmacher <metze@samba.org>
Mon, 11 Dec 2006 16:36:30 +0000 (11 16:36 +0000)
committerGerald (Jerry) Carter <jerry@samba.org>
Wed, 10 Oct 2007 19:29:07 +0000 (10 14:29 -0500)
tree14722fce9337a17de37c781a8c056d87e4b792a5
parentea111795f4016916473ccc05d23c6655e6af1207
r20107: don't segfault when the server didn't send a supportedMech in a negTokenTarg

this happens because we send 1.2.840.113554.1.2.2 before 1.2.840.48018.1.2.2
in the negTokenInit. And w2k's spnego code redirects us to use 1.2.840.48018.1.2.2
and then we start the our spnego engine with 1.2.840.48018.1.2.2 and in the then following
negTokenTarg w2k don't send the supportedMech (which means it aggrees in what we've choosen)

metze
source/auth/gensec/spnego.c