3 ms·
Situations like these are why I like the networking system of Qubes OS. With it you can plug any network VM in front of your applications, usually TOR but there
by jeroenhd 6y ago
Situations like these are why I like the networking system of Qubes OS. With it you can plug any network VM in front of your applications, usually TOR but there's no reason why it can't be a corporate VPN, and let the rest of your software use that as their uplink.
Vendor VPN software will probably never be fixed; there is no financial incentive for playing nice with other vendors and incompatibilities in upgrades means their locked-in customers who need to work with other companies are only incentivized to also upgrade. Sadly a system like Qubes' or using VMs will probably be the only way to combine VPNs from different companies and/or vendors for while...
- Fnoord 6y ago> Sadly a system like Qubes' or using VMs [...] You can do the same with Docker, too. Or an external machine plus some routing voodoo.
- jeroenhd 6y agoThat's true, although routing a browser or generic application through Docker can be difficult sometimes. There's also not that many of these shitty VPN clients with Linux support, which is a major pain.
- Fnoord 6y agoNo idea which shitty VPN clients these are. Am aware of frontends only (also I currently mostly use macOS as client), as well as Sshuttle (provides VPN over SSH via CLI). You can run a container running a browser such as Firefox or Browsh linked to a WireGuard or OpenVPN container. But you can do it without that, too. Have a different user use a different (virtual) interface, for example. Layer 7 packet filter could achieve it as well.
- jeroenhd 6y agoAh, my problems with these systems is that they usually rely on some proprietary Cisco protocol or OpenVPN with an extra authentication daemon. I agree that open source VPNs are thankfully to run, thankfully.