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? thanks, Michael > -----Original Message----- > From: Constantin Kaplinsky [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 28, 2001 10:50 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: TightVNC 1.2.2 released > > > Hello, > > TightVNC 1.2.2 has been released today. This version does not feature > a lot of great new features, but I think improvements in its Win32 > part may worth the upgrade. Here is a brief list of changes over > 1.2.1: > > - Win32 server: long-standing Win9x resource consumption problem has > been fixed. Now the server thread does not use blocking I/O, and > therefore is always ready to process messages from the VNCHooks > DLL. > > - Win32 server: now built-in HTTP daemon may be enabled and disabled > interactively from the Advanced Preferences dialog (this setting > is saved in new "EnableHTTPDaemon" registry key). > > - Win32 server: changes in layout and text of the Advanced > Preferences dialog. > > - Xvnc: Minor bugfix which should prevent potential dereference of a > NULL pointer. > > - Unix viewer: Now viewer window would be raised on remote beep > (bell) event by default. New -noraiseonbeep option and the > "raiseOnBeep" resource set to False disable this behaviour. > > - One more packaging option for the Unix source: ready to build > archive with Zlib and JPEG libraries inside. > > - Other minor fixes and cleanups. > > New version is available from the usual place: > > http://www.tightvnc.com/ > > TightVNC project now has a mailing list hosted by SourceForge.net: > > https://lists.sourceforge.net/lists/listinfo/vnc-tight-list > > I'd like to thank all the people who reported bugs, contrubuted > patches and ideas, or supported TightVNC development by any means. > > -- > With Best Wishes, > Constantin > --------------------------------------------------------------------- > 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 > --------------------------------------------------------------------- --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
