{"id":318,"date":"2006-08-25T03:40:09","date_gmt":"2006-08-25T03:40:09","guid":{"rendered":"https:\/\/www.darknet.org.uk\/2006\/08\/anonymous-connections-over-the-internet-using-socks-chains-proxy-proxies\/"},"modified":"2015-09-09T19:40:38","modified_gmt":"2015-09-09T11:40:38","slug":"anonymous-connections-over-the-internet-using-socks-chains-proxy-proxies","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2006\/08\/anonymous-connections-over-the-internet-using-socks-chains-proxy-proxies\/","title":{"rendered":"Anonymous Connections Over the Internet – Using Socks Chains Proxy Proxies"},"content":{"rendered":"

Introduction<\/strong><\/p>\n

This tutorial is an attempt to help you re-route all internet winsock applications in ms windows trough a socks chain, thus making your connections much more anonymous.<\/p>\n

Theory<\/strong><\/p>\n

The more different hops you make your data jump, the more difficult it will be to trace it back. take this route for example:<\/p>\n

you –> socks1 –> socks2 –> socks3 –> … –> socksx –> target<\/p>\n

People who want to trace you will have to contact x persons to ask their them for their logs. chances are one of them didn’t log… and if they logged, the ip seen by each host\/socks is the ip of the previous host\/socks in the chain.<\/p>\n

This works for:<\/p>\n