Remove ProtonVPN

Site Development Tool Suggestions
231

on iOS/macOS

iOS and MacOS should not be lumped together.

This topic is about ProtonVPN on MacOS. iOS can and should be ignored in this thread, it is off topic and muddying the waters.

Here is what the initial user who reported the problem reported:

When using ProtonVPN on MacOS with the kill switch active, the killswitch failed to provide protection in these 3 common situations:

  1. During Startup [1]
  2. When the user intentionally or unintentionally clicks disconnect (from the VPN server) [2]
  3. When changing servers [3]

#3 is by the most egregious and most serious in my opinion. Switching from one server to another is a situation where users absolutely expect to be protected and other VPNs do offer protection in this scenario. #2 is also a problem, but not quite as bad.

It’s unreasonable to blame a VPN provider for an OS level problem. So if #1 affects all vpn providers on MacOS, Proton should not be blamed for #1. But in the case of #2 and #3, these are common scenarios a killswitch should protect against, which Proton could protect against, but currently doesn’t. There is no evidence #2 & #3 are due to OS limitations, and no evidence has been provided that other VPNs have the same flaws on MacOS.

I suspect we can probably all agree on two things:

  1. For every OS where killswitch functionality is possible, recommended VPNs should provide a fully functional killswitch.
  2. For OSes where a fully functional killswitch is not possible, a killswitch should still be provided to the greatest extent that is practical, and limitations should be disclosed and documented.

Mullvad and iVPN currently meet the above criteria afaict. Proton does not, but it is within Proton’s power to fix that, so their removal would be temporary (assuming they have a good-faith interest in offering a functional killswitch).

I personally do not want to see Proton de-listed, but if the alternative is to lower our established standards and bend a criteria specifically for Proton, then I think temporarily de-listing them may be the “least bad option” until they choose to remedy the situation. edit: by far the best solution would be for Proton to just fix the problem :crossed_fingers:

  1. (this may be a limitation of MacOS outside of Proton’s control) ↩︎

  2. no evidence this is an OS issue, other VPNs on MacOS don’t appear to have this problem ↩︎

  3. no evidence this is an OS issue, other VPNs on MacOS don’t appear to have this problem ↩︎