I don't think either of these is a good idea for several reasons: 1) How is a screen saver password any different that no screen saver with a VNC password? VNC passwords are just as easy to set/change as a screen saver password. If the server initiated the screen saver before the client connected, this is just a different way to do password access, but it is less secure and more complicated.
2) Screen savers are usually a bad idea with remote software because they are highly graphical in nature. Most remote control software disables them when the client connects, exactly the opposite of what you want to do. 3) I don't see any benifit to multiple passwords at first glance. The VNC password is easy to change, so just change it for a bit if you want to give it to someone and then change it back once they are done. Maybe if you gave more information about what you wanted to do, I could be wrong on this one, but I need more info. On Wed, 28 Nov 2001, Michael Rybarski wrote: > I would like to see the server lock the workstation or bring the screen > saver up (password protected) before viewer gets the screen. That way I > could have null passwords at VNC level and still require authentication if > workstation is set with password protected screen saver. > > Also, how about multiple passwords per VNC server so one can keep one > password to him/herself and give out other passwords to people on temporary > basis. > > Perhaps someone already have implemented the above already? --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
