-Malt Liquor
RDP over TOR
#1
Posted 12 September 2006 - 04:41 PM
-Malt Liquor
#2
Posted 12 September 2006 - 05:00 PM
#3
Posted 13 September 2006 - 01:59 AM
socat TCP4-LISTEN:1234,fork SOCKS4A:localhost:someserver.com:3389,socksport=9050
Now when you connect to localhost:1234 your connection will be proxied through Tor to someserver.com:3389
Probably won't do you much good under windows, no idea if it works under Cygwin. According to the Tor Win32 Howto:
For applications that support neither SOCKS nor HTTP, take a look at SocksCap, FreeCap, or the Hummingbird SOCKS client. (FreeCap is free software; the others are proprietary.)
For more information how to Torify other applications in detail visit the Torify HOWTO.
Freecap
#4
Posted 13 September 2006 - 03:59 AM
One problem here is that without a lot of messing around, the Microsoft RDP client refuses to connect to localhost - it's kind of sensible since why would you want a remote desktop on your local machine...You can use socat to torify almost any application like so:
socat TCP4-LISTEN:1234,fork SOCKS4A:localhost:someserver.com:3389,socksport=9050
Now when you connect to localhost:1234 your connection will be proxied through Tor to someserver.com:3389
Probably won't do you much good under windows, no idea if it works under Cygwin. According to the Tor Win32 Howto:For applications that support neither SOCKS nor HTTP, take a look at SocksCap, FreeCap, or the Hummingbird SOCKS client. (FreeCap is free software; the others are proprietary.)
For more information how to Torify other applications in detail visit the Torify HOWTO.
Freecap
From memory, you need to copy MSTSC.EXE and MSTSC.DLL into a different directory, and then run MSTSC.EXE under compatibility mode for a Win9x machine or something stupid like that. I don't remember exactly, but I do know it's possible since I've had to use it over SSH tunnels in the past.
#5
Posted 13 September 2006 - 08:13 AM
One problem here is that without a lot of messing around, the Microsoft RDP client refuses to connect to localhost - it's kind of sensible since why would you want a remote desktop on your local machine...
From memory, you need to copy MSTSC.EXE and MSTSC.DLL into a different directory, and then run MSTSC.EXE under compatibility mode for a Win9x machine or something stupid like that. I don't remember exactly, but I do know it's possible since I've had to use it over SSH tunnels in the past.
Next time try connectiong to 127.0.0.1 (or 127.65.34.99 or whatever) that works for me.
#6
Posted 13 September 2006 - 09:58 AM
One problem here is that without a lot of messing around, the Microsoft RDP client refuses to connect to localhost - it's kind of sensible since why would you want a remote desktop on your local machine...
From memory, you need to copy MSTSC.EXE and MSTSC.DLL into a different directory, and then run MSTSC.EXE under compatibility mode for a Win9x machine or something stupid like that. I don't remember exactly, but I do know it's possible since I've had to use it over SSH tunnels in the past.
Next time try connectiong to 127.0.0.1 (or 127.65.34.99 or whatever) that works for me.
Thanks for the ideas I am going to run a few tests to insure I am using the proxy.
BinRev is hosted by the great people at Lunarpages!











