Silent crash on win10

[DirkHeinke]

Hi,

I just tested your version of cntlm and when the first requests arrives, the process just stops. Are you using this on Windows?

Thanks
Dirk

[versat]

I mainly use Windows 7 for testing, sometimes Linux (Ubuntu). I do not have a Windows 10 system for testing but would be very interested in fixing this.
Did you use the installer?
Could you run cntlm.exe -v or cntlm.exe -T debug.log in the Cntlm directory and see if there is any problem reported?

[DirkHeinke]

I run it with -v but there is not more Output. If I run it with -S, it doesn't Crash, but is very slow. Does that help?

[versat]

Hmm, strange. There should be much debug output with -v.
Do you mean lowercase -s (single thread instead of multi threading) or really the uppercase -S?
If it is an issue with creating threads i can have a look what could be the reason on Windows 10.

[DirkHeinke]

Oh, sorry. I used -s

[versat]

Ok, so it is some issue with the multithreading, but i can imagine many reasons.
I will see if i find anything suspicious.

[versat]

I have tested cntlm on Windows 10 but only against a normal proxy (no NTLM). While it is not possible to test very much this way, what i have seen looked ok. I have also not found anything in the code that could be problematic on Windows 10.
If someone can test and maybe even debug cntlm on Windows 10 against a NTLM Proxy that would be great.

[cstrong]

Howdy!
I am working with a NYC municipal government agency that uses NTLM authentication and we are really stuck! We are using the old SourceForge version of cNTLM on win10 but observing that npm (binary) downloads simply halt after awhile. I would like to volunteer to do some debugging on this, on the win10 platform. We may be a good test case, because we use CentOS7.5, Ubuntu 18.04, MacOS, Windows7 and Windows10 and need cNTLM on all of them! I just wanted to say hello and check in with the maintainers. It appears this is the healthiest and most up-to-date version of cNTLM out there! I might be able to spend some actual code-level debugging time and maybe even make a pull request in the future, but I wanted to check in first and see what is the highest value-add from your perspective to move forward. It is not easy, but theoretically possible I could get the agency to make a contribution as well (though that would have to be done through a NYC-registered firm; we would have to figure out logistics...) cheers

[versat]

I am working with a NYC municipal government agency that uses NTLM authentication and we are really stuck! We are using the old SourceForge version of cNTLM on win10 but observing that npm (binary) downloads simply halt after awhile. I would like to volunteer to do some debugging on this, on the win10 platform. We may be a good test case, because we use CentOS7.5, Ubuntu 18.04, MacOS, Windows7 and Windows10 and need cNTLM on all of them!

I would highly appreciate any help with debugging cNTLM and it would be great to see PRs improving cNTLM further and fixing issues.
Although several issues were fixed it still does not run absolutely stable on Windows. I am not sure if it has to do with Cygwin which itself might contain bugs. But what could be resolved inside cNTLM should be resolved there.

[kamil321]

I've had the same problem. Try debugging with gdb and check the exception stacktrace for any strange dlls. In my case it turned out that a realtime virus scanner was causing every pthread_create to crash, but only with x64 libs. Rebuild on 32-bit cygwin resolved the issue.

[jschwartzenberg]

How hard would a port to MinGW be? Note that WSL works quite well.

I have not yet been able to get pacparser itself to compile on Windows (in Cygwin) btw.

[versat]

@fralken did some great work fixing some bugs, also related to the multithreading.
Can you test your setup again?

[jschwartzenberg]

We are using the old SourceForge version of cNTLM on win10 but observing that npm (binary) downloads simply halt after awhile.

I saw this on RHEL too, but indeed the threading fixes solved it.

[fralken]

We can consider this issue solved.