Depending on your threat model that’s unacceptable. You can do a variety of things to give you better guarantees. You could have your torrenting client only attached to the local socks proxy of your VPN. Mullvad does this.
You could use something like Portman to ensure that the torrenting software can only talk to the VPN.
If you’re very sensitive you could use something like qubes to ensure that a virtual machine running your torrenting program can only talk to your VPN and your VPN can only talk to the VPN endpoints.
Depends on your threats. And your appetite for failure. If they make a programming error and it goes out clear are you okay with that? How much do you want to avoid leakage? Is this just data hygiene, in that case good enough is good enough.
If Windows hiccups and forgets to enforce you’re always on VPN requirement, is that okay?
Mistakes will happen especially around changes in updates. So if there’s a large windows update coming and it changes the network stack security model or momentarily you know switches out drivers will your networking go to a standard pathway and avoid the VPN? Is that okay? In that rare scenario are you okay with being clear? If not then you might want to look at something that has more layers. Like forcing a client to use a proxy which then uses the VPN. So that way if the VPN’s off the proxy won’t work in your traffic won’t go anywhere.
But if you’re happy with your current model then you’re happy
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Depending on your threat model that’s unacceptable. You can do a variety of things to give you better guarantees. You could have your torrenting client only attached to the local socks proxy of your VPN. Mullvad does this.
You could use something like Portman to ensure that the torrenting software can only talk to the VPN.
If you’re very sensitive you could use something like qubes to ensure that a virtual machine running your torrenting program can only talk to your VPN and your VPN can only talk to the VPN endpoints.
deleted by creator
Depends on your threats. And your appetite for failure. If they make a programming error and it goes out clear are you okay with that? How much do you want to avoid leakage? Is this just data hygiene, in that case good enough is good enough.
If Windows hiccups and forgets to enforce you’re always on VPN requirement, is that okay?
Mistakes will happen especially around changes in updates. So if there’s a large windows update coming and it changes the network stack security model or momentarily you know switches out drivers will your networking go to a standard pathway and avoid the VPN? Is that okay? In that rare scenario are you okay with being clear? If not then you might want to look at something that has more layers. Like forcing a client to use a proxy which then uses the VPN. So that way if the VPN’s off the proxy won’t work in your traffic won’t go anywhere.
But if you’re happy with your current model then you’re happy
Spoken like a true cyber security professional.
Great answer.
Is your ISP watching you that closely??
deleted by creator
I reckon you are fine