How do I have Windows XP Pro create a SSH tunnel for Port 3389 Automatically?

[InlineFive]

As stated by someone farther down this thread that he has set up a computer to automatically create a SSH connection whenever someone access it with Port 3389 (Remote Desktop/Assistance). He hasn't replyed that thread so I thought I would ask here.

I am wondering how I can have my Windows XP Professional SP1 desktop do the same thing as his computer. I have been looking around online but still don't know if I need any special software or how I should go about setting up this Automated SSH Tunnel. Please keep it simple as I am not a programmer.

Thanks in advance! 🙂

-Por

 

[PowerMacG5]

There is no need to route Remote Desktop over SSH (Secure SHell), or SSL (Secure Sockets Layer). The Terminal Services protocol that Remote Desktop uses has encryption built in. It is already secure.

 

[InlineFive]

Originally posted by: KraziKid
There is no need to route Remote Desktop over SSH (Secure SHell), or SSL (Secure Sockets Layer). The Terminal Services protocol that Remote Desktop uses has encryption built in. It is already secure.

But according to the thread I posted above the password is not encrypted. Besides, better safe then sorry.

 

[PowerMacG5]

Originally posted by: PorBleemo

Originally posted by: KraziKid
There is no need to route Remote Desktop over SSH (Secure SHell), or SSL (Secure Sockets Layer). The Terminal Services protocol that Remote Desktop uses has encryption built in. It is already secure.

But according to the thread I posted above the password is not encrypted. Besides, better safe then sorry.

As far as I know, it is. I believe it uses MSChapv2 to encrypt the password and handle the handshake, just as done with Microsoft's implementation of the PPTP protocol. It encrypts all packets using 128 bit, or 56 bit true encryption depending on what version of the OS is on the client.

 

[InlineFive]

Originally posted by: KraziKid

Originally posted by: PorBleemo

Originally posted by: KraziKid
There is no need to route Remote Desktop over SSH (Secure SHell), or SSL (Secure Sockets Layer). The Terminal Services protocol that Remote Desktop uses has encryption built in. It is already secure.

But according to the thread I posted above the password is not encrypted. Besides, better safe then sorry.

As far as I know, it is. I believe it uses MSChapv2 to encrypt the password and handle the handshake, just as done with Microsoft's implementation of the PPTP protocol. It encrypts all packets using 128 bit, or 56 bit true encryption depending on what version of the OS is on the client.

If it does that would be really cool. From some other people I was getting the impression that it wasn't encrypted. Thanks Krazi! 🙂

 

[sciencewhiz]

You can install ethereal (ethereal.com) and sniff your outgoing packets. That should answer it once and for all.