On 3/1/11 8:06 AM, Sebastiaan Breedveld wrote: > Then how does it work? If I start: > > Xvnc :10 > > then I read on the server: > client requests security type VeNCrypt > but the client tries to authenticate with VncAuth. > > The server then complains that neither Password or PasswordFile is set. > > > Apart from that, the vncserver script persistently adds the --rfbauth > flag to ~/.vnc/passwd.
Please search the list archives for more detail, as we've discussed this in depth in the past weeks. The VeNCrypt security type is now implied, and the default server security type order has VncAuth first. Thus, if you don't pass -SecurityTypes to either the client or the server, the default will be to use VncAuth. To default to a different security type, you must start the server with the -SecurityTypes parameter and either omit VncAuth or move it to later in the preference order. As I mentioned, though, TLSVnc also needs ~/.vnc/passwd. -rfbauth is no longer used to enable VNC auth. It is simply used to tell Xvnc where to find the password file. Thus, that option should have no effect unless VNC auth is enabled. ------------------------------------------------------------------------------ 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
