From fa24196d0d5c7373317894865b7a88d972762101 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Tue, 10 May 2005 11:04:04 +0000 Subject: r6705: let the gensec module decide if messages can be signed and sealed in a different order than a strict request - reply sequence Note: we should also fix the client code... metze (This used to be commit 0a61d1f65150546f7a7582512ca010d156f963bf) --- source4/auth/ntlmssp/ntlmssp.c | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'source4/auth/ntlmssp/ntlmssp.c') diff --git a/source4/auth/ntlmssp/ntlmssp.c b/source4/auth/ntlmssp/ntlmssp.c index 254736688b..ac007ae3ab 100644 --- a/source4/auth/ntlmssp/ntlmssp.c +++ b/source4/auth/ntlmssp/ntlmssp.c @@ -183,6 +183,11 @@ static NTSTATUS gensec_ntlmssp_update(struct gensec_security *gensec_security, gensec_ntlmssp_state->have_features |= GENSEC_FEATURE_SESSION_KEY; } + /* only NTLMv2 can handle async replies */ + if (gensec_ntlmssp_state->neg_flags & NTLMSSP_NEGOTIATE_NTLM2) { + gensec_ntlmssp_state->have_features |= GENSEC_FEATURE_ASYNC_REPLIES; + } + return status; } -- cgit