cryptostorm / cstorm_widget Goto Github PK

From a member:

"When I Disconnect It always gives me a windows error. and it leaves my adapter with the gateway set to proxy not obtain auto"

Also report of Bitdefender being angry with the widget - some hints it's upset with script-y activities, which could be related to the firewall rulechains added by the webRTC leakblock syntax?

It seems the widget client hasn't been updated for about two years. As a result, many library and dependency files are now outdated and vulnerable. Do you plan to release new version of the software. I am a long-time customer.

Do you have any plans to develop your own desktop client for Linux-based operating systems? It would be great to have one client application which is lean (no binaries) and comes with dependencies which can be locally met on my operating system of choice. It would also be great if such client would have a simple boxes to select between various obfuscation techniques such as stunnel, openconnect (run openconnect on top of OpenVPN to prevent DPI inspection), SSH, obfs4, XOR, multihop, etc.

No steps to reproduce as it can happen out of the blue while running the client. CS Twitter operator (assuming p_j) has passed it on to df for review.

Since Windows sucks with program debugging I have no log to upload.

I would like to be able to use the *.ovpn files CStorm uses outside of the widget/client.

Have been having this issue for a bit. When I disconnect a session, the widget 8/10 times

hangs and eventually begins 'Not Responding'. I have to exit it with task manager, and then typically have to restart my computer afterwards as the widget doesn't finish setting my DNS back to normal. Even when the widget does seem to work normally upon shutdown and appears to have restored all of my settings, I have to restart my computer to visit any webpages as they will all result in "we're having trouble finding that site" type messages until I reboot.

I also have recently been getting the pop-up in the attached image when connecting recently, but I am unsure if it's related to the other issue or not.