mullender
No NTLMv2 support
There is some code (e.g. ComputeResponse) which looks like unfinished NTLMv2
support and which is never called. To get proper NTLMv2 responses
ComputeResponse should be fixed to use TargetInfo from type1 messages, various
functions should pass TargetInfo around and
create_NTLM_AUTHENTICATE_MESSAGEcreate_NTLM_AUTHENTICATE_MESSAGE should call
ComputeResponse (with proper Time). This is very least, probably more things
need to be changed.
Original issue reported on code.google.com by [email protected] on 15 Sep 2014 at 5:57
no new features are being developed, only minimal maintenance.
If you're willing to make a potential support of NTLMv2 going on, submit a
patch with the modifications you're talking about, and I will apply it, so
that's something already done the next NTLMv2 contributor won't have to do :)
Original comment by [email protected] on 2 Oct 2014 at 2:10
Hi all,
We are really interesting in this solution. Currently all our servers are stop
to support NTLMv1 and moved to support only NTLMv2. Based on this all our
python script stop work. It is drama...
Could you advice may be about work around or temporary solution?
Could you estimate time needed to fix this issue?
Best regards,
Yuri Avdoshin
Original comment by [email protected] on 5 Dec 2014 at 3:58
There is nobody working anymore on python-ntlm. The project is stalled, unless
someone take it back. No solution, sorry.
Original comment by [email protected] on 18 Dec 2014 at 2:59
Hey, there's a Python 3 compatible fork here, feel free to add pull requests:
https://github.com/trustrachel/python-ntlm3
Original comment by [email protected] on 8 Jan 2015 at 1:45
If the project is stalled, it would be great if that was mentioned on the home
page. As it seems that the above referenced project is more alive,, to at least
mention the existence of that fork would be helpful and be a way forward. Also
to provide users a new place to engage.
Original comment by [email protected] on 11 Jan 2015 at 1:42
The only guy of the team that still answer to mail lost its access to change
project status and/or front page or grant me the permission to do so. Anyway,
google is closing google code in the end of 2015, fork will mechanically become
more popular, until one really rise up and shine. So the problem will solve
itself.
Shame of the original team that screw the passing of the torch.
Original comment by [email protected] on 12 Mar 2015 at 9:17
Hello @mullender ,
I found python-ntlm-fixed at Python packages repository and it seems that you're the author: https://pypi.python.org/pypi/python-ntlm-fixed
Given the NTLMv2 support issue, how good is it with its urllib2 authentication handler as an alternative to requests-ntlm with its python-ntlm3 / python-ntlm dependency? (sample code would be much appreciated)
If not good enough, do you think we can make use of the work done by @ianclegg in ntlmlib (https://github.com/ianclegg/ntlmlib) to add NTLMv2 support to either of the two packages?
