flawed windows build? #323
Description
Hello Andy!
First of all I'd like to thank you for the very useful application that has been helping me a lot!
Yet it has some space for improvement: I have met a distilled situation which is AFAIU related especially to the ck-client-windows-amd64-v2.12.0 build.
I do have a VPS with ck-server-linux-amd64-v2.12.0 running and some place (with residential IP in RU) where I tested ck-clients 2.12 built for linux, windows and android. And the outcome is quite stable: windows build is stuck at the very beginning while both linux and android clients works ok. I tried every possible "BrowserSig", some "EncryptionMethod"s (plain, aes and chacha20) and two "ProxyMethod"s (ss and openvpn) and it does not affect the outcome at all. Client reports "wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond" and server ""error reading first packet: read error after connection is established: ... i/o timeout".
Could there be a signature within window's network/crypto libraries/stacks which triggers DPI? Is it possible to build with other libraries?
P.S. Several days ago windows client stopped working with 'firefox' BrowserSig. That time switch to 'chrome' had helped.