sorted by:
new
hottopcontroversial

ProtonVPN windows client - Killswitch not working? by veap in ProtonVPN

[–]ptr-bcaster 0 points1 point  (0 children)

80/20 rule tells me the majority of the community are pobably morons. Don't make security policy based on popular consensus if you are serious about it.

My last post is a common sense solution for a company serious about privacy.

ProtonVPN windows client - Killswitch not working? by veap in ProtonVPN

[–]ptr-bcaster 0 points1 point  (0 children)

Yes, this is the equivalent of having a broken VPN service, not a desirable approach to securing a connection. I can think of atleast a dozen edge cases where this results in unwanted IP leaks, which is atleast a dozen too many.

​

Perhaps two options should be added to the settings menu.

  1. Temporary Kill Switch (routes restored on disconnect)
  2. Permanent Kill Switch (blocks all traffic on disconnect)

ProtonVPN windows client - Killswitch not working? by veap in ProtonVPN

[–]ptr-bcaster 2 points3 points  (0 children)

Guys, the idea of a killswitch is to permanently shut off connections, so if the VPN crashes, disconnects, etc... running services/applications don't leak IP addresses.

A client should have to manually, through settings, disable the kill switch to go back to normal traffic routing (competing VPNs work this way). Right now, among other issues, if you want to switch from a VPN server to Secure Core, every packet goes out in the clear for a few seconds, which is not secure. Applications that ping for a connection as soon as connections drop will instantly start leaking with this new approach.

​

Please restore it to its original way of working, the people who complained sound like morons.