This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Problems with OpenSSH in win32.
- From: "Ross Boulet" <ross at rossb dot com>
- To: "'Brian Chase'" <networkr0 at cfl dot rr dot com>, <cygwin at cygwin dot com>
- Date: Mon, 29 Mar 2004 16:01:57 -0600
- Subject: RE: Problems with OpenSSH in win32.
- Reply-to: <cygwin at cygwin dot com>
> -----Original Message-----
> From: cygwin-owner On Behalf Of Brian Chase
>
> Are you sure of this statement? The reading I have done on TightVNC
> tells me it encrypts passwords only and doesn't have any SSH
> capabilities. I'd be happier if I were not correct, but I'd
> like to read
> some documentation proving me wrong to confirm it.
>
> Alejandro Lopez-Valencia wrote:
>
> And
> > that's the reason why I suggested TightVNC, performance is
> acceptable
> > with a 56K modem link, and it defaults to using SSH
> tunneling, so for
> > practical purposes you obtain a cheap VPN.
> >
> > And now back to your original broadcast.
> >
>
I may be talking out of school here, but I've used ssh to tunnel other IP
based protocols such as POP3, SMTP, and printing. The application doesn't
have to know about ssh. ssh just has to be told which IP ports to forward.
For example:
ssh -L 515:127.0.0.1:515 myhost
Tells ssh to start a session with myhost and forward IP port 515 to the same
port on myhost.
I would assume the same thing can be done for TightVNC using whatever ports
it requires.
Ross
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/