Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Valid point but there's nothing stopping you setting up your own VPN (either on a small VM from someone like Linode or, if you're paranoid enough, a cheap 1U server bought off ebay and placed in a colo facility).

For the single point of failure issue (which is also valid)... just setup two or more VPNs :) And, in an emergency, you can always fall back to the underlying connection.



Setting up your own VPN does not solve the traceability problem, unless you happen to find a colo facility that does business in face-to-face cash transactions only.

If you use Linode to set up a VPN, Linode knows your personal and Linode IP, knows when you access their network, and knows your name and billing info. If compelling by warrant they will turn that over to law enforcement.


I setup an own VPN on a dedicated server, payed it prepaid and faked the customer data. This should be really hard to trace back to me.


If your hosting company hasn't saved your access logs for the purchase. Otherwise you just added one step to the process.


Well, they probably log, but maybe you find an open or public wifi to join ;)


also they probably just log URLs and IPs, but not the POST requests.


Sorry, I didn't realise removing traceability was the goal. If you want that, you're better off with tor not a VPN.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: