First, securing VNC (or anything) is a process, not a matter of simply using some program or other. Several parties to this list have pointed out other aspects besides securing the communication stream that are known to be points of attack; for example, VNC's use of the windows registry to store passwords.
Second, for the part of the problem that is limited to the communications stream itself, solutions using SSH and/or ZeBeDee are possible, but somewhat complicated; requiring you to a FAQ as noted. Or you could take the simple approach and use my contribution, ZNC, which is equivalent to the ZeBeDee solution but requires only running the correct client server, and doesn't require a FAQ. http://people.we.mediaone.net/ddyer/znc/zvnc.html --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
