On Tue, Mar 01, 2011 at 11:25:41AM +0100, Sebastiaan Breedveld wrote: > Hi all,
Hello, > 2) When using the VeNCrypt security type, the ~/.vnc/passwd is not > necessary, yet the user is asked to create one. Same when using the > securitytype none. The script now checks for the -SecurityType option > and checks wether VeNCrypt type or none is specified. (That is, I am in > the assumption that the VeNCrypt type does not use the vnc password.) You are right, vncserver script shouldn't create passwd file unless it is needed. passwd file is needed only when at least one of those types is specified (case insensitive): VncAuth or TLSVnc or X509Vnc By default server allows VncAuth and TLSVnc. Correct approach is: 1. if -SecurityTypes parameter is not specified, create .vnc/passwd 2. if -SecurityTypes contains at least one of three types specified above, create .vnc/passwd 3. otherwise don't create .vnc/passwd Note in 1. and 2. cases you need to pass -rfbauth parameter, otherwise Xvnc won't find password file. With this checks vncserver will create .vnc/passwd only when needed. Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ 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
