On Sat, 2012-12-01 at 23:14 +0000, John Case wrote: > On Fri, 2 Nov 2012, grarpamp wrote: > > >>> I don't agree. torsocks is still useful to prevent identity correlation > >>> through circuit sharing. Pushing all traffic through Trans- and DnsPort > >>> is not the answer. > >> > >> Also, I don't want all of my applications using Tor -- just some of > >> them. Using Tails or TransPort wouldn't allow me to do this. > > > > Some people do run multiple Tor's, jails, packet > > filters, and apps. Largely to get around current > > Tor limitations. Those people don't have this > > singularity problem/position that you assume. > > Torsocks is not required in that instance. > > > There has to be a better way to simply "make an ssh connection over ToR". > > I don't want to run all of tails just to make a single ssh connection (2 > minutes to properly fire up vmware, massive cpu use, laptop gets hot, fans > running, everything else comes to a crawl). > > I don't want to run a full-blown tor relay installation with all the bells > and whistles and then maintain that full blown environment, watch > advisories, run periodic tests, test for dns leakage, blah blah. > > I want this: > > cd /usr/ports/net/torssh > make install > torssh u...@host.com > > Am I the only person that wants/needs this ? > > I understand that you can't go down the road of "make a custom tor app for > everry possible client app that people want to run", but come on ... ssh ? > If there was just a single app to do this for, it would be that, right ?
Just put this in your .ssh/config: ProxyCommand socat STDIO SOCKS4A:localhost:%h:%p,socksport=9050 You do need to run the Tor daemon as a client, which I'm not sure if you're okay with. -- Sent from Ubuntu _______________________________________________ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk