You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the payload offsets of the domain name and hostname, due to some NTLM
servers expecting a zero offset denotion when the negotiation flags
don't include the flags for supplying the domain and workstation meta.
This is what cURL does, so it's seemingly safe here. #facepalm
- Spec: https://msdn.microsoft.com/en-us/library/cc236641.aspx
- "DomainNameBufferOffset field SHOULD be set to the offset from the
beginning of the NEGOTIATE_MESSAGE to where the DomainName would be
in Payload if it was present."
- "WorkstationBufferOffset field SHOULD be set to the offset from
the beginning of the NEGOTIATE_MESSAGE to where the WorkstationName
would be in Payload if it was present."
- cURL forcing a 0 length and offset: https://github.com/bagder/curl/blob/curl-7_46_0/lib/curl_ntlm_msgs.c#L364-L370
0 commit comments