IÂ’ve been running an Tor server (middleman only) for a while and IÂ’ve been wondering about using FreeCap and an account on an SSH server that has a SOCKS proxy to tunnel my Tor serverÂ’s connections over an SSH tunnel to the SOCKS proxy running on that SSH server. Hopefully I explained that clearly, if not maybe this will help to visualize it:
TOR Server – FreeCap – SSH Tunnel – SOCKS proxy – [Out to internet]
I have tried testing this and it works. Clients are able to connect to my TOR server, and in trying it myself there is no noticeable increase in latency (ping time to the SSH server is < 15ms, and the server has a fast CPU and faster network connection). As far as I can tell, based on netstat and the like, when I client connects to my server, their circuit is built
through the SSH tunnel and then to the SOCKS proxy server, and then out on the internet to the next Tor server in the circuit. When data comes back to my Tor server, it first comes through the SOCKS proxy on to the SSH tunnel, and then to my Tor server, then to the client or other Tor server in the chain.
I get the feeling that this should be more secure because:
My ISP canÂ’t monitor my Tor serverÂ’s outgoing connections.
Even of the SSH/SOCKS serverÂ’s connection was monitored, other peoples Tor circuits should be mixed in with my Tor serverÂ’s connections.
Any thoughts on this?
Also, just so there is no confusion, I am an authorized user of the SSH/SOCKS server, and I am not under any bandwidth or CPU usage
constraints. My access to the server is very fast and the tiny bit of latency seems trivial. IÂ’m only interested in the security implications of this approach. Thanks!
Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.
