"Linonut" <linonut@xxxxxxxxxxxxx> wrote in message
news:sRsej.42969$vt2.1997@xxxxxxxxxxxxxxxxxxxxxxxxx
>* Antonio Murphie fired off this tart reply:
>
>> "Roy Schestowitz" <newsgroups@xxxxxxxxxxxxxxx> wrote in message
>> news:35279476.aPtAkqZxjB@xxxxxxxxxxxxxxxxxx
>>
>> In other words.... it's just like "Remote Desktop" which has been
>> bundled
>> with every Windows computer for the past 8 years.
>
> Nope. First, X has been around in one form or another for 23 years.
> SSH has been around for 12 years.
Thanks for the history lesson but what does it matter? The issue isn't
which protocol has been around the longest... it's functionality. In the
end the user has a graphical connection to the remote computer. Whether ssh
has been around 12 years and RDP only 8 years isn't relevant. The issue is
administering a remote computer.
> Second, SSH can be used to encrypt or tunnel all sorts of protocols:
>
> http://en.wikipedia.org/wiki/Secure_Shell#History
>
> terminal
> ftp
> rsync
> cp
> remote monitoring
> file system
Yeah I know how it works. At work we may need to connect remotely to any
one of over 30,000 remote servers that we administer.
With RDP (the Microsoft implementation) users can also connect to "sound",
"printers", "serial ports", "disk drives" and etc. So it makes the notion
that you can optionally tunnel FTP, cp, etc. somewhat redundant since RDP
also supports this.
> Not to mention VPN support and usage as a proxy.
>
> I like this one, using your vaunted "Remote Desktop" protocol:
>
> ssh and rdesktop. Three computers, the computer that will run
> rdesktop and ssh, a computer used to obtain access to a remote
> network, and the last will be the computer you want rdesktop to
> display.
>
> "ssh -L3389:mytarget.mycompany.net:3389 sshtarget.mycompany.net"
>
> Just log into the middle computer and do
> nothing on it. Open another shell from the first computer running ssh
> and type "rdesktop localhost". This example uses the middle computer to
> port forward 3389 from the end computer to the first computer. If on
> Windows, run ssh using another local port, e.g.
>
> "ssh -L3390:mydesktop.mycompany.net:3389 sshserver.mycompany.net"
Yep. Been there and done that.
> Start the native Windows Remote Desktop client and type localhost:3390
> to
> remote into "mydesktop.mycompany.net"
>
> GNU/Linux and OSS wins (get it? get it?) again!
Not a strong start for the New Year, eh?
--
Posted via a free Usenet account from http://www.teranews.com
|
|
