from Anonymous_TorPerson@lemmy.ml to piracy@lemmy.ml on 19 Sep 2023 14:13
https://lemmy.ml/post/5171004
It looks like I have nothing more to add to the conversation than the fact that almost every vpn which has a free plan doesn’t allow torrenting. That’s it folks. Ignore the post. Gonna not delete it because, well for the archieve ig
Here’s what I learnt, almost every vpn which has a free version doesn’t allow torrenting. Not even protonvpn, however if apparently atlasvpn allows it, but atlasvpn didn’t work for me, so I am gonna go take a nap.
I was wondering how you torrent using qbittorrent
and manage to stay anonymous. I realize I can use a VPN, but VPN networks can fail. Apparently, there is a kill switch which can be applied so that qbittorent
would kill all processes when the VPN is disconnected, I was wondering how one could do this. I live in a country where torrenting might be cracked down, so I just want to be secure and not take any chances.
Also, I realize I should not torrent over the tor network but what about VPN are they built to handle such a load?
PS: I won’t download more than 300mbs per day.
#piracy
threaded - newest
This has been discussed before in more depth other places. I’m going to give just a brief overview primer.
You can use a variety of techniques to prevent your VPN from leaking. But nothing is guaranteed. You have to weigh the inconvenience of setting up fail safes, versus the bad things that could happen if it fails.
You could use a container that requires access to the internet through your VPN. So if your VPN fails the container has no network access.
You could use a socks proxy which goes over the VPN, and configure your software to only use that socks proxy. Mullvad makes this easy, not sure about proton.
You could use a operating system like Qubes which would run your software inside of a VM that could only talk to another VM which is set up with the VPN. This is probably the most secure, but also the most inconvenient.
Whatever method you use, you could always run a tattletale program inside of that environment, and if it sees it has a public IP address suddenly, it kills the device.
So everything’s a trade-off.
To expand on the container/vm idea, for someone that’s never done such a thing before, installing whatever OS u want (windows or other) in virtual box then setting the network get internet only from the vpn would be a very secure but not all that hard to do.
The easiest way for a beginner would however be to use a VPN that have its own software with built in kill switch, then you select whatever program you want killed if the vpn goes down, and it just exits that program. (If your paranoid research DNS leaks first)
I like the idea. It’s really well explained. I would caution against trusting VPN internet kill switches with your Liberty and freedom. They’re well designed, and well intentioned, but many things can cause them to malfunction.
Operating system updates, network driver updates, even adding a weird Wi-Fi device, can all do messy things with the network stack and rules. And may even briefly subvert the always on VPN setting.
For good day to day hygiene it’s perfectly adequate. But if your activities put you at risk, and that risk is high, don’t trust always on kill switch by itself.
In my country nobody is cracking down, so no VPN.
You can also argue a VPN might maker you more of a target, so if you don’t need it -don’t use one.