What should we require of VPN providers on macOS?

[ignoramous]

@jonah

While this is no longer a technical issue for us, because of the criteria change above

I don’t get why this is no longer a technical issue?

From Apple’s documentation, it seems that includeAllNetworks flag will prevent the traffic leak scenario on exit server changes that Proton is hitting on macOS?

Even then, it isn’t clear why Proton’s macOS app should leak on exit server changes at all, without includeAllNetworks flag set. If Proton’s using WireGuard… nothing about the official implementation strikes me as requiring recreating the VPN tunnel (which is where I presume the leak comes from) on exit server changes.

(… with the caveat that I’m not an experienced iOS developer) It seems like enforceRoutes is another ‘killswitch’ like API that may work.

@ignoramous

@ph00lt0

Apple’s architecture makes it nearly impossible to make a functioning kill switch.

This is a misleading statement. NetworkExtension docs do mention that for VPNs using includeAllNetworks (a form of a ‘killswitch’) will prevent traffic from bypassing the VPN for advertised routes, for example, when apps may “scope” their traffic to a particular network interface

I’m aware of Mullvad’s blog post that claims that the includeAllNetworks flag results in permanent connectivity loss on iOS when the VPN app that sets the flag is killed by the platform’s app -updater.