What's new
Troll Kingdom

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

i feel out of touch with everything

Ishcabittle

Ishcabittle

Well-known member
if I can't ssh -L 3390:127.0.0.1:3389 into you, you don't exist to me right now.

cygwin makes a badass sshd_config file, i'll tell you that much right now boy howdy.
 
Think about us while touching yourself and then you'll be back in touch with everyone..err or at least yourself.
 
Ishcabittle said:
if I can't ssh -L 3390:127.0.0.1:3389 into you, you don't exist to me right now.

cygwin makes a badass sshd_config file, i'll tell you that much right now boy howdy.
Click to expand...
Can you even do that? Can you ssh into rdp port? What does that do?
 
Well since 127.0.0.1 is the host machine that would be prudent. You would change it to the PC you wish to remote control while keeping the source port.
 
Grammour Boy said:
Can you even do that? Can you ssh into rdp port? What does that do?
Click to expand...

Yeah - use cygwin as your sshd server, then hit the box with the aforementioned command. ssh will map 3390 on localhost to 3389 on the remote machine, you would then start up RDP and point it to localhost:3390 and pow - secure connection to your windows box.

ever since i learned how easy it was to sniff out passwords during RDP login i switched an ssh solution for my XP box.

Sorry i told GB something about security - we're all going to find out boxes hacked when we get home. Or we'll notice it happening right in front of us if we are home. Either way, GB's a hacking queen.
 
Ishcabittle said:
Yeah - use cygwin as your sshd server, then hit the box with the aforementioned command. ssh will map 3390 on localhost to 3389 on the remote machine, you would then start up RDP and point it to localhost:3390 and pow - secure connection to your windows box.

ever since i learned how easy it was to sniff out passwords during RDP login i switched an ssh solution for my XP box.

Sorry i told GB something about security - we're all going to find out boxes hacked when we get home. Or we'll notice it happening right in front of us if we are home. Either way, GB's a hacking queen.
Click to expand...
Just trying to get this straight:

ssh -L 127.0.0.1:3390:<remote machine ip>:3389

In effect you create a secure ssh connection to the <remote machine ip> and then you tunnel an RDP connection through that ssh session, thereby making your RDP connection bulletproof secure against sniffing? Is that correct?

(I assume this requires a sshd server/daemon running on the local machine, correct? I haven't found a good sshd server for windows yet. I haven't looked at Cygwin much).

Tell me more about password sniffing during RDP login. Isn't Microsoft smart enough to make RDP login session encrypted? Oh, wait, they're not!
 
yeah. pron rulez.

you can also ssh -2C 3390:192.168.1.X:3389 [email protected] to forward ports from a third machine on the network (192.168.1.X).

basically, you can block every port but 22 on your lan and still get at every service from the wan. WHEEE!!!!!
 
Grammour Boy said:
Just trying to get this straight:

ssh -L 127.0.0.1:3390:<remote machine ip>:3389

In effect you create a secure ssh connection to the <remote machine ip> and then you tunnel an RDP connection through that ssh session, thereby making your RDP connection bulletproof secure against sniffing? Is that correct?

(I assume this requires a sshd server/daemon running on the local machine, correct? I haven't found a good sshd server for windows yet. I haven't looked at Cygwin much).

Tell me more about password sniffing during RDP login. Isn't Microsoft smart enough to make RDP login session encrypted? Oh, wait, they're not!
Click to expand...

no M$ doesn't like securing their remote sessions. makes perfect sense. cygwin is the shit, fyi, take a look at their setup.exe installer - it'll grab just about everything for you, including openssh.

so the format:

ssh -L 3390:localhost:3389 user@serverIP/serverdomain

command local-forwarding local port:local port's IP:remote port - user@serverIP

you're basically saying, hey, any traffic going to port 3390 on localhost should now be routed to port 3389 on user@serverIP. So RDP thinks that you're hitting 3390 on your own box (which you can't) but ssh is all like, "Whoa, now, i'm supposed to route that local port to this here remote port on this remote box! Shit!" and shit.
 
i guess the whole point of the thread (before we got into ssh) is that i haven't been hangin' with my TK peeps nearly enough for my sanity's sake.

i miss y'all.
 
peeps-yellow.jpg


peeps.
 
Very nice, indeed!

The neat thing is that you don't require an sshd server running on the remote machine at all.

You can use a third-party remote machine such as a linux box sitting in some back office somewhere running sshd and then tunnel localhost:3390 traffic through that sshd server and then route it to the remote pc's 3389 rdp destination port. And voila!

Neat stuff. The first time I used ssh tunneling I was almost as ecstatic as you .
 
Well, you need sshd running on at least one machine... but when you tunnel in you can specify the routing to any other machine on the same subnet. So yeah - forward port 22 to some linux box on your LAN and you have remote access to every machine you can remember the IP of.
 
You must log in or register to reply here.
Back
Top