On 03/01/2011 12:13 PM, DRC wrote: > > As far as checking for the VNC password, we're no longer requiring > "VeNCrypt" to be specified in the -SecurityTypes parameter, so checking > for that won't work. The correct approach is to check whether > -SecurityTypes is not specified -- or -- whether -SecurityTypes is > specified and contains (case insensitive) "VncAuth". If either of those > conditions is true, then and only then should vncserver check for the > existence of the VNC password. > Looking at it again, the vncserver script adds --rfbauth automatically, so a more structural change is necessary:
- if no options are given, force VeNCrypt, and do not use --rfbauth anymore - force VeNCrypt by specifying SecurityTypes, and do not use --rfbauth in that case Or am I misunderstanding something? Greetings, Sebastiaan ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
