Jason Forand created HTTPCLIENT-1624:
----------------------------------------
Summary: NTLM resp in v2 is way too big
Key: HTTPCLIENT-1624
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1624
Project: HttpComponents HttpClient
Issue Type: Bug
Components: HttpAuth
Affects Versions: 4.4 Final, 4.3.6
Environment: Running from a linux box, connecting to a windows 7
machine.
Reporter: Jason Forand
When connecting to a windows host using NTLM authentication, if the windows
host passes back the
NEGOTIATE_UNICODE
REQUEST_TARGET
NEGOTIATE_SIGN
NEGOTIATE_SEAL
NEGOTITATE_LAN_MANAGER_KEY
NEGOTIATE_NTLM
NEGOTIATE_ALWAYS_SIGN
TARGET_TYPE_DOMAIN
NEGOTIATE_NTLM2_KEY
NEGOTIATE_TARGET_INFO
UNKNOWN_4
NEGOTIATE_128
NEGOTIATE_KEY_EXCHANGE
NEGOTIATE_56
flags, (in this case the offending flag is NEGOTIATE_NTLM2_KEY) the type3
message is generating an ntresp using
http://davenport.sourceforge.net/ntlm.html#theNtlmv2Response when it should be
generating according to
http://davenport.sourceforge.net/ntlm.html#theNtlm2SessionResponse
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
