I want to give Mozilla my money for this, but it's really annoying how unfriendly its implementation is.
1: https://www.mozilla.org/en-GB/products/vpn/#faq-compatibilit...
I want to give Mozilla my money for this, but it's really annoying how unfriendly its implementation is.
1: https://www.mozilla.org/en-GB/products/vpn/#faq-compatibilit...
I can't speak for Mozilla, but we have our own desktop and mobile apps because it enables us to do more privacy-preserving things with a higher assurance. Consider for instance DNS leaks, Teredo leaks, IPv6 leaks, esoteric DHCP directives that can hack your routing tables, and so on.
And these are just a few of the things we were early in mitigating correctly. Consider also the tight relationship between UX and security, and it is clear that we can't rely on "generic VPN clients" to always agree with our design and security preferences. That doesn't mean they are wrong and we are right of course. It's just that we have a very specific mission.
One architecture decision we made for our app was to write its backend in Rust, and integrate tightly with the firewalls on Windows, macOS, and Linux. It facilitates stability and therefore reduces the risk of states where data leak outside of the tunnel. Check it out, it's open source. As all security-related things should be.
I should perhaps have been clearer when I referred to generic VPN clients, I was talking about the original WireGuard implementation by Jason Donenfeld, not just some random software, which I would hope you agree is a (sufficiently) secure implementation when used by technically proficient users? I do appreciate that there are reasons for having a specific client for your service, and it is absolutely necessary for those who are new to VPN apps, but I would hope you appreciate the reasons for providing implementation-agnostic WireGuard/OpenVPN config files, since your own service does so?
Regardless, thanks again for the work you're doing in this sector, and best of luck for the future.
There are plenty of VPN clients, some by big enterprise-y networking companies, that at least historically have behaved in ways that leaks the user's traffic when interfaces change, on DHCP issues, tunnel disconnections. It's just easier to make our own app and be able to say what it does and doesn't. And that nothing will change tomorrow because of someone else's design decision. :)
Any reason why you don't use a PPA or something to auto-release updates? I've postponed an update quite a few times because the friction of going to your website, downloading it, and then upgrading the package is just a bit too much in certain situations.
Other than that my only gripe with the app is that I can't close it from the app indicator, but have to re-open it, click on the settings, and then choose "quit app".
Any deviation from the standard implementation, open source or not, is a hindrance.
Not an employee I just like the service.
Sure, I could make it work with a separate Linux server running your app and some routing but that's far more work than most other VPN providers.
I'm fine with warnings in your UI about connections with these protocols being "less secure" like how Zoom handles E2E with phones.
Mozilla seems to make it really hard to pay them for goods and services.
Sad that PIA tanked their rep because their Linux support was top notch. They even had a script that would set up NetworkManager profiles for you.