4 ms·

Hi, thanks for the response. I'm a big fan of Mullvad's approach to creating a VPN, and I'm hopeful that more companies will follow in your path. I've been usin

Hi, thanks for the response. I'm a big fan of Mullvad's approach to creating a VPN, and I'm hopeful that more companies will follow in your path. I've been using your service for a few months now, and I'm really satisfied with it. 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.

kfreds 6y ago
Thanks! Yes, I completely recognize that many users prefer to download a generic configuration file for WireGuard or OpenVPN. In our case we want to support that use case. At the same time encouraging use of our own app allows us to invent to a much greater extent. And mitigate risks. 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. :)