> 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.
The registry isn't that secure on 9x clients, but on NT/2000 (don't know about XP) you can set user permissions on certain reg keys. I've tried this with WinVNC - allowing on administrations and the system access to the WinVNC3 branch and below - and it seems to work fine. If anyone want to try this on a number of PCs so we can spot any bugs, that would be very helpful. Would the VNC settings for Windows be better stored in a file (like unix?). On systems with NTFS, you could set permsisions to only allow services, admin and system to view the file...... but is that any more secure than CACLing the reg? It doens't help anyone on 9x though, sorry!! Later, Richard --------------------------------- Richard Harris Environment IT, NCC Ext 4509 --------------------------------- "Service, price , quality: pick any two." --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
