Re: NTLM - Not Telling Linux Much

FWIW, I'm the guy who wrote Re^2: More NTLM. I hadn't looked at that code in ages; in fact, as soon as I got it working, I dropped the whole thing. Proof of concept, I suppose.

I did just now run my simple test script and it still works. I am sorry I do not know the version of the IIS server I am running against.

I am attaching my debug output at the bottom. One difference I noticed is that my initial response is short and sweet:

LWP::Protocol::collect: read 24 bytes
[download]

.. while your first response is not.

LWP::Protocol::collect: read 566 bytes
LWP::Protocol::collect: read 1736 bytes
LWP::Protocol::collect: read 1380 bytes
LWP::Protocol::collect: read 351 bytes
[download]

Make of that what you may. Good luck!

Full output:

LWP::UserAgent::new: ()
LWP::UserAgent::request: ()
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking .net for cookies
LWP::UserAgent::send_request: GET http://**url sanitized***
LWP::UserAgent::_need_proxy: Not proxied
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 24 bytes
LWP::UserAgent::request: Simple response: Unauthorized
LWP::Authen::Ntlm::authenticate: authenticate() has been called
LWP::Authen::Ntlm::authenticate: In first phase of NTLM authentication
LWP::Authen::Ntlm::authenticate: Returning response object with auth h
+eader:
Authorization NTLM TlRMTVNTUAABAAAAB7IAAAQABAAgAAAAAgACACQAAABtaXBqQ1Q
+=
LWP::UserAgent::request: ()
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking .net for cookies
LWP::UserAgent::send_request: GET http://**url sanitized***
LWP::UserAgent::_need_proxy: Not proxied
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 24 bytes
LWP::Protocol::http::request: Keep the http connection to **url saniti
+zed***:80
LWP::UserAgent::request: Simple response: Unauthorized
LWP::Authen::Ntlm::authenticate: authenticate() has been called
LWP::Authen::Ntlm::authenticate: In second phase of NTLM authenticatio
+n
LWP::Authen::Ntlm::authenticate: Returning response object with auth h
+eader:
Authorization NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAQABABwAAAA<sn
+ip>
LWP::UserAgent::request: ()
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking **url sanitized*** for cook
+ies
HTTP::Cookies::add_cookie_header: Checking .net for cookies
LWP::UserAgent::send_request: GET http://**url sanitized***
LWP::UserAgent::_need_proxy: Not proxied
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 121 bytes
LWP::Protocol::http::request: Keep the http connection to **url saniti
+zed***:80
HTTP::Cookies::extract_cookies: Set cookie ASPSESSIONIDQABTQSCR => FIM
+DDGABNLLJPKIIMJKIDGBN
LWP::UserAgent::request: Simple response: Found
[download]

Comment on Re: NTLM - Not Telling Linux Much Select or Download Code

Replies are listed 'Best First'.
Re^2: NTLM - Not Telling Linux Much by aufflick (Deacon) on Feb 20, 2006 at 23:43 UTC
Interesting. I guess your IIS is returning much smaller tokens/seed/whatever. It may even be that it is a different algorithm and thus my response is not satisfying the requirement. Unfortunately I don't have access to the server but I will do some more investigation.	[reply]