Re: Remote Desktop directly to another computer on the network

Another reason I like SSH (or VPN if it floats your boat as they say) is for
simple secure file transfers. I generally use a free SFTP client called
WinSCP for that to access my home SSH server. No need to even callup RDP
just to transfer files. If you have the bucks WebDrive is nice because you
can actually map a remote folder through the SSH tunnel. I do that, ie. use
WebDrive, with a persistent SSH tunnel to my brothers SSH server. He has a
static business class IP/account with his cable ISP. Its great for file
transfers, ie. he puts a file in the common folder and I can grab it or vice
versa...

The other positive, at least in my mind, with a SSH link is the use of
private/public key pairs (I use a 2048-bit RSA key pair) for authentication
versus a password (strong or otherwise). The remote party must have the
private key that matches the servers public key or the connection is not
made period. The keys are further protected by a strong pass phrase. In my
setup, and my brothers, password authentication is strictly prohibited and
disabled. So the SSH link is encrypted from the get-go and the remote user
can only logon to the SSH server with a valid private key and strong pass
phrase. I like that...

Anyway, we all have our preferred methods and opinions. The discussion is
good...

Later...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"auser" <auser@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5166A126-6344-4F4C-98F2-5D50CA2A459B@xxxxxxxxxxxxxxxx
i am not really disagreeing with you... each has its own advantages.. but
when that 486 crashes... you'll think to yourself... maybe multiple ips
aren't such a bad idea... lol


"Peter" wrote:

if you are using encryption in rdp 5.1 or higher, you will not be able
to
view the stream. You would be no more likely to crack the encryption
than
you
would be to crack ssl encryption.. or ssh for that matter.

That is exactly my point.

VPN gives you only that advantage, that you do not have to manage your
router forwarding ports, when you add more remote PCs.
And you do not have to remember which PC uses which port.

But on the other hand, you have to maintain a VPN server, as you have
pointed it out.
(I actually do it VPN way. My VPN server is running on old 486 Linux PC,
very low maintanance)


.

Relevant Pages

  • Re: IPSec VPN into XP Pro
    ... This page has more information concerning the XP VPN... ... As far as SSH is concerned, I just think its a whole lot easier for home users like myself to setup ... a few consumer grade routers and the problems encountered getting a PPTP tunnel through them... ... > tunnel and set up secure redirections via command line. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Relationship SSH <-> VPN ??
    ... I'm not sure whether you're most probably referring to *SSL* vs. VPN, ... and not SSH. ... A Virtual Private Network, VPN, is a secure "network" built on top of ...
    (comp.security.misc)
  • Re: Relationship SSH <-> VPN ??
    ... I'm not sure whether you're most probably referring to *SSL* vs. VPN, ... and not SSH. ... A Virtual Private Network, VPN, is a secure "network" built on top of ...
    (comp.os.linux.security)
  • Re: Relationship SSH <-> VPN ??
    ... I'm not sure whether you're most probably referring to *SSL* vs. VPN, ... and not SSH. ... A Virtual Private Network, VPN, is a secure "network" built on top of ...
    (comp.security.firewalls)
  • Re: Relationship SSH <-> VPN ??
    ... I'm not sure whether you're most probably referring to *SSL* vs. VPN, ... and not SSH. ... A Virtual Private Network, VPN, is a secure "network" built on top of ...
    (comp.security.ssh)
Loading