SocksChain is a useful utility that will help you hide your IP when browsing the Internet.
SocksChain allows to connect to any Internet service through a chain of SOCKS or HTTP proxies to hide the actual IP address.
It also possible to work with a programs that are not designed to support SOCKS protocol directly.
SocksChain can function as a usual SOCKS-server that transmits queries through a chain of proxies.
SocksChain can be used with client programs that do not support the SOCKS protocol, but work with one TCP-connection, such as TELNET, HTTP, IRC... (FTP uses 2 connections). And your IP-address will not be seen in the server's logs or mail headers.
SocksChain transmits the TCP-call of a client program in such a way that it successively goes through a chain of proxies.
SocksChain itself is connected only with the first element of this chain. That one in its turn is connected with the second and so on...
So, to track where the query was initiated from with the help of server logs is very complex. To do that, one should analyze the logs of all intermediates one by one in the reverse order.
If somewhere the logs are not kept, the thread will be lost. Theoretically it provides a high degree of anonymity. But it affects the speed of data transmission as it is inversely proportional to the chain length.
SocksChain allows to connect to any Internet service through a chain of SOCKS or HTTP proxies to hide the actual IP address.
It also possible to work with a programs that are not designed to support SOCKS protocol directly.
SocksChain can function as a usual SOCKS-server that transmits queries through a chain of proxies.
SocksChain can be used with client programs that do not support the SOCKS protocol, but work with one TCP-connection, such as TELNET, HTTP, IRC... (FTP uses 2 connections). And your IP-address will not be seen in the server's logs or mail headers.
SocksChain transmits the TCP-call of a client program in such a way that it successively goes through a chain of proxies.
SocksChain itself is connected only with the first element of this chain. That one in its turn is connected with the second and so on...
So, to track where the query was initiated from with the help of server logs is very complex. To do that, one should analyze the logs of all intermediates one by one in the reverse order.
If somewhere the logs are not kept, the thread will be lost. Theoretically it provides a high degree of anonymity. But it affects the speed of data transmission as it is inversely proportional to the chain length.
