Repository navigation
Send the SPNEGO mechListMIC in the SMB2/3 NTLM session setup - #2339
Conversation
|
Nice one |
|
+1, I needed this PR for something recent and fun to authenticate to Windows 11 Insider Preview 29704.1000. |
|
Added MsvAvFlags.MIC_PRESENT (0x00000002) whenever SMB3 includes an NTLM AUTHENTICATE_MESSAGE MIC. This follows MS-NLMP §2.2.2.1 (https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/83f5e789-660d-4781-8491-5f8c6641f75e), which defines that bit as indicating client-provided message integrity, and §3.2.5.1.2 (https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/f9e6fbc4-a953-4f24-b229-ccdcc213b9ec), which specifies how servers detect the MIC field. @azoxlpf if you are ok, we can merge it |
|
LGTM 🙂 |
|
merging now, Thanks! |

This PR makes the SMB2/3 NTLM session setup send the
SPNEGO mechListMIC(and the AUTHENTICATE MIC that goes with it), whichMS-SPNG 3.3.5.1makes mandatory when NTLM is the preferred mech. Without it, recent versions of Windows Server answersSTATUS_INVALID_PARAMETERas soon as the credentials are valid, theLDAP GSS-SPNEGObind already did this,smb3.loginnow does the same.Before & After :