Other people have suggested binding the client to the vpn interface. In rtorrent this is very easy. It may be easy in other clients.
stupid_asshole69
The isp generally doesn’t care if you’re doing p2p. Some use it as a sales tactic to get you to move up to their top tier bandwidth plans though. They handle complaints about your p2p that have been investigated by some group contracted by the rights holders who usually say they have the file or want the file and take note of the ip that offers or accepts the file and then send that information to the group responsible for that ip.
In the case of your home ip, your isp receives the letter and sends you a letter in kind complying with all the laws they’re subject to. This usually has the threat of legal action and termination of service.
In the case of your vps ip, the vps provider complies to the full extent of the law. In some places with a three strikes or similar style of enforcement they may just forward it to you. They may use it as an excuse to ditch you if you’re a problem customer for them. It’s completely within the realm of possibility that they happily provide all the information they have on you, but that usually only when the police get involved.
In the case of your p2p vpn service they often have the ability to say “we don’t know which of our customers we’re connecting from that ip and have no way of finding out”. It’s a dead end for them.
Air has worked well for me. Proton is fine as long as you’re careful about what metadata you give them. Both do port forwarding.
In general, it would be a bad idea to use the same vpn account or service for p2p that you use for browsing or whatever. So maybe don’t do that.
If you want it to look right you need to take it to a shop.
It’ll be expensive, but they’ll get it so close that only someone who knows the car inside and out, or knows how to clock paint differences will recognize it.
If you don’t care how it looks then just scuff everything and use a rattle can.
Comedy option: precisely scrape and sand the damaged area, use glue to attach gold leaf to it then clear coat over. Beater kintsugi!
Someone else asked “safe from what?” And that’s the real question.
In lieu of an answer to that though, no. It isn’t. The whole point of using a vpn to do p2p is to accomplish three things: traffic anonymization, legal protection and encrypted data transfer.
A vpn on a vps doesn’t anonymize your traffic because the vps is in your name. The vps provider is likely in compliance with kyc laws and will happily give you up to the law the moment they come knocking. If you’re using a domain with it it’s even easier to check that it’s you by looking at the whois records. On the off chance you’re getting a vps with enough storage and transfer included to act as your seedbox without kyc using cash or monero or something you’re likely paying more than the 2-3$ a month that the p2p vpns tend to charge.
A vpn on a vps most likely doesn’t provide you any legal protection either! Generally speaking, privacy focused vpn providers use nonpersistent systems where the secrets that can be subject to lawful intercept by the authorities are not stored on the systems hard drive and have protections against being read out of ram. Not only are almost all vpses generally held to be vulnerable to having their ram contents read by the provider, it is extremely unlikely that you set up openvpn without a configuration file on disk that contains your secret. This is just one example of a well documented vector of legal attack against a vpn, there are many. Paying an expert in legal attacks takes the onus off you.
A vpn on a vps doesn’t even accomplish encrypted data transfer, since the tunnel is between your pc and your vps, not whatever the vps connects to. Encryption keeps untrustworthy devices upstream of you from reading the data you send and receive. You might have prevented your untrustworthy isp devices from viewing your data, but you didn’t prevent untrustworthy vps provider devices from viewing your data. Even if your vps is trustworthy, the infrastructure it uses is the same infrastructure whose built in lawful intercept backdoors were compromised last year with no firm resolution. This wouldn’t matter nearly as much if your traffic were anonymized or had the shield of a crew of computer security experts running the system you use as a vpn, but as outlined above, you don’t.
Running your own vpn on a vps is cool, and I’m glad you have that ability, but it’s a lot like building your own car from scratch. It is possible, and a phenomenal learning experience, but not the suggested route for anyone.
Use a p2p vpn service instead. It’s much cheaper and better in almost every way.
Assuming you feel safe and the car is meeting your needs:
When the car is no longer able to reliably function and it’s negatively impacting your daily life. Think about that person you know who’s got to pour oil or water into her old jalopy to go from home to work and back again.
When the annual, average cost of repairs and maintenance becomes more than the cost of the payment plus expected maintenance of a replacement. If this frequently happens to you then someone else should be choosing your car.
Shut down the vm, mount the vm disk, mv the files over, unmount the vm disk, start the vm.
That works because nowadays software doesn’t run itself, the system chooses what to run (sometimes at the users request).
When you shutdown the vm, there is no virtual computer interacting with the files on the vms disk. When you mount the vms disk, you’re just telling your system to treat the file that represents the vms disk as a filesystem. When you move the files to it, you’re just copying the files to the file that represents the vms disk respecting its filesystem then deleting the originals. When you unmount the vms disk you’re telling your system to wrap it up and let go of the file that represents the vms disk. Starting the vm is just telling your system to pretend that it has a fake computer whose disk is that file you mounted and wrote to which just so happens to have some new files in it, imagine that!
There’s another person saying you probably can’t figure out if the files you have are malware. I won’t go that far, but the reason most people don’t setup forensic environments (that’s generally what the computing environment you’ve set up is called when you’re doing what you’re doing) for their warez and instead raw dog it is that they have some security software and process they trust and if they get catch some kind of problem they plan on just restoring from backup.
You do have backups, right?
It’s rare for user targeted malware to have persistence, most of that technology is targeted at infrastructure like switches, edge and servers, so a wipe and restore is almost always a perfect fix.