On Wed, 4 Apr 2001 13:22:23 +0100, you wrote:
>> I got vnc locally working on port 25 on my network after a huge amount of
>> research and piecing together incomplete advice from many sources.
>
>This is a bad idea. The firewall is probably there to prevent outside
>machines accessing things they shouldn't inside your network. Forcing VNC
>to operate over one of the three open ports in the firewall is equivalent to
>just taking the firewall down, or opening up the normal VNC port.
VNC still requires a password, and I don't think many hackers would
attempt looking for VNC on 25, but security by obscurity is marginally
better than none at all. A simple telnet to 25 would reveal its existence.
>It's much better to get SSH installed and open the SSH port, then tunnel
>whatever you like (VNC, telnet, FTP, etc) through that, instead.
I don't see any likelyhood of SSH happening. The issue is academic now
that I got pcAnywhere back, but port 25 remains the smtp service and is
additionally a backup port for urgent non-command line maintenance via VNC
should the need ever arise.
Cheers,
Andy.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Haveland-Robinson Associates Tel. +36 30 223 2158
Budapest 1015, Donati u.17 fszt.1, Hungary Web: www.haveland.com
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
