alternatively it can be built from source (or sourced unofficially from the AUR).
More interestingly, it looks like there has been some preliminary groundwork done on making a flatpak version, with the goal of publishing it on Flathub eventually.
That’d be another +1 for Mozilla VPN since Mullvad seems unwilling or unable to. Not sure how they’ll get around the restrictions though.
1 Like
I don’t have any deep understanding of the ways in which flatpak makes it more difficult or what limitations are introduced, beyond a basic udnerstanding of Flatpak sandboxing and isolation, but it has already been demonstrated to at least be possible for a VPN app to work as a flatpak. There is a working (currently unofficial) ProtonVPN flatpak on Flathub already.
I wonder how similar the Mullvad and Mozilla apps are, if they are somewhat similar, it seems that Mozilla publishing a flatpak version might make it more likely that Mullvad would reconsider their stance towards flatpak and build on or borrow from Mozilla’s work.
Followup: I was able to build the flatpak locally, following some of the steps discussed in this github issue. But I don’t actually use or subscribe to Mozilla VPN, so I can’t actually test the connection. But I was able to build, install, and launch the flatpak:
1 Like
The best way to have different proxy for each container is with mozilla vpn with their integration , but you can manually add proxies if your vpn offers socks5/http/htpps proxies , mullvad offers socks5 proxies
2 Likes