this post was submitted on 08 Aug 2025
403 points (85.2% liked)
Privacy
3546 readers
163 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 9 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Their Linux VPN client might as well not exist. No kill switch and it randomly disconnects/crashes. Sometimes it completely borks networking necessitating a reboot, which I guess can be better than just leaking your IP?
Isolating the VPN into docker + gluetun should (should) solve that particular issue.
I’ve never heard of this before! I read this a bit: https://pimylifeup.com/docker-gluetun/
What is the benefit here? I have no experience with containers, so I’m not really sure what I’m encapsulating there.
A container runs the utility in an isolated environment without having to alter your base system's packages, dependencies, etc. Assuming the bork that necessitates a reboot is not a kernel or hardware issue, this would mean that if you get hit with that issue again in a container, what dies is the container itself, rather than your system as a whole. So you're isolating 1.- package management 2.- network config and (potentially) 3.- "blast radius".
(That said, this is the first time I've ever heard that Proton would bork the networking to the point of requiring a whole system reboot.)
Thanks for explaining!
Don't thank me yet, as I said, this is the first time I've ever heard of this kind of bork, so I'm hoping this would fix / sidestep it! :p
I was thanking you for the explanation. I need to spend some time playing with containers and understanding how to manage applications that way.
I just use plain old openvpn configs. Once my credit runs out ill switch to mullvad. They were the best option for a time, but that changes.
tf you mean? kill switch does work, doesn't randomly disconnect and it doesn't really bork it for me. skill issue? guess my distro based on my pfp