Main list for questions, suggestions, bug reports etc about Tight VNC

Dietrich Restemeyer | 17 Nov 2011 19:05

Re: ssh tunnel

Am 14.11.2011 10:34, schrieb John Serink:
> You need a port forward entry to the server on port 22, ssh.
> Once you open the tunnel, you tvnc through the tunnel using tcp port
> forwarding. make sure TVNC on your server is configured to allow
> connections on 127.0.0.1 (localhost) and make sure you sshd is
> configured to allow tunnelling to localhost.
>
> Cheers,
> John
>
>
And please configure your sshd N O T to use port 22 but any other unused 
port.
Port 22 will often be scanned by bad guys.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

headers

John Serink | 17 Nov 2011 23:20

RE: ssh tunnel

Good point.
Port 22 will be continually interrogated by internet bots to look for logins like user: root pw: 12345 or pw:
admin. Once the bot has found a machine like that, it can take it over.

You can set freesshd to run on any port you want, so do that and then adjust your router's port forward accordingly.

Cheers,
John

-----Original Message-----
From: Dietrich Restemeyer [mailto:dietrich.restemeyer <at> googlemail.com]
Sent: Fri 11/18/2011 7:05 AM
To: vnc-tight-list <at> lists.sourceforge.net
Subject: Re: ssh tunnel

Am 14.11.2011 10:34, schrieb John Serink:
> You need a port forward entry to the server on port 22, ssh.
> Once you open the tunnel, you tvnc through the tunnel using tcp port
> forwarding. make sure TVNC on your server is configured to allow
> connections on 127.0.0.1 (localhost) and make sure you sshd is
> configured to allow tunnelling to localhost.
>
> Cheers,
> John
>
>
And please configure your sshd N O T to use port 22 but any other unused 
port.
Port 22 will often be scanned by bad guys.

(Continue reading)