3 ms·
All traffic is encrypted + goes through the VPN in a docker image with firewall configured to shutdown the moment the VPN disconnects. The IP of the cloud VM i
by hbt 9y ago
All traffic is encrypted + goes through the VPN in a docker image with firewall configured to shutdown the moment the VPN disconnects.
The IP of the cloud VM is never exposed. Only the VPN's.
If you're worried about dropbox type surveillance, you store the data in an encrypted drive.
- halter73 9y agoBut couldn't ask the same question of the VPN that the grandparent post asked of the cloud provider? Namely, won't they turn your info over just as fast as an ISP?
- hbt 9y ago1) The VPN's IP will be used by more than one person. (i.e a pool) 2) use a VPN that has a reputation for not keeping logs and turning people over. https://thatoneprivacysite.net/vpn-comparison-chart/ https://thatoneprivacysite.net/vpn-comparison-chart/
- hartator 9y agoWhy not just use a VPN then? A cloud VM does seem overkill.
- ad_hominem 9y agoI haven't seen this project before but a few reasons come to mind at first glance 1) Looks like it also runs a headless Transmission client, so you could use it as a seedbox 2) It can be tricky to configure VPNs correctly so that if the VPN connection goes down, your traffic doesn't spill over onto the clearnet. If this Docker image ensures that aspect works correctly then that's helpful. 3) It's a little complicated to setup a VPN connection on a personal computer just for BitTorrent use, without having other traffic (e.g. browsing) spill over onto the VPN. Setting this all up on a segregated remote box and connecting to the headless Transmission client mitigates that.
- captainmuon 9y agoAh, I thought this was about running your own VPN server in the cloud!