4 ms·
From the features page: > We use only VPN protocols which are known to be secure - IKEv2/IPSec and OpenVPN. If you want to use Wireguard, consider Mullvad.
by OJFord 7y ago
From the features page:
> We use only VPN protocols which are known to be secure - IKEv2/IPSec and OpenVPN.
If you want to use Wireguard, consider Mullvad.
- richardkmichael 7y agoIn Dec 2018, ProtonVPN said Wireguard support is forthcoming: https://protonvpn.com/blog/wireguard-donation/ https://protonvpn.com/blog/wireguard-donation/ As of Oct 2019, no updated status: https://protonvpn.com/blog/wireguard-donation/#comment-9236 https://protonvpn.com/blog/wireguard-donation/#comment-9236
- twojacobtwo 7y agoApparently it is expected by the end of this year, as noted in a recent reddit [1] thread: >protonvpn 1 point 6 days ago >Thanks for your suggestion, we will consider this. We will plan to implement Wireguard as a protocol by the end of this year. [1]https://old.reddit.com/r/ProtonVPN/comments/eo2k9m/eta_on_wireguard_support/ https://old.reddit.com/r/ProtonVPN/comments/eo2k9m/eta_on_wi...
- craftyguy 7y agoOpenVPN and IPSec clients exist, why is ProtonVPN reinventing the wheel? This ProtonVPN advertisement wouldn't have been 'necessary' if they had used and supported an existing client for these protocols.. but then again, they wouldn't have had this ad on 'hacker' 'news' if they had..
- OJFord 7y agoLower barrier to entry for non-technical users? Marketing (by being in app-stores, and thus gaining visibility & being suggested for 'users like you')?
- craftyguy 7y agoThose arguments don't hold any weight. They could have forked the OpenVPN for Android app (which is some GPL license, don't remember which), thrown in their own branding and default config, and not shipped a proprietary mess to customers. Instead they went the proprietary mess route.
- himinlomax 7y agoI haven't looked at the app, but my guess is things like exit point selection, account management, troubleshooting and performance indicators.
- prophesi 7y agoNot sure what exit point selection is, but I don't see why any of those features can't be added upstream to a FOSS OpenVPN client/server.
- himinlomax 7y agoIt's simply selecting where packets exiting the VPN are routed. > but I don't see why any of those features can't be added upstream to a FOSS OpenVPN client/server Could be simply because none allows this in the first place. And then the selection may be very service-dependent. In any case, their app is now open source, so why is this an issue anyway?
- prophesi 7y ago> In any case, their app is now open source, so why is this an issue anyway? My issue is that countless VPN companies are re-inventing the wheel, when they could just be contributing to open-source in the first place. It's obviously in their best interests from a security & trust standpoint to start from an already open & well-audited platform. Everyone wins when bugs are squashed and new features are added; and the licensing lets them keep their branding/ui for the app they deploy.