On 9/7/10 4:53 AM, Adam Tkac wrote: > Imagine this situation: > > server: > - admin starts it with following parameter: > "-SecurityTypes VeNCrypt,Plain,TLSNone,None" > > client: > - started with following parameter > "-SecurityTypes VeNCrypt,TLSNone,Plain" > > In this situation client will select VeNCrypt security type because > server has it enabled and it is the first on the client's list and > then client selects TLSNone subtype, because it is more preferred than > Plain subtype. > > Second scenario, server is started as before. > > client: > - started with "-SecurityTypes VeNCrypt,X509Plain,VncAuth" > > Now client selects VeNCrypt security type, as before, but then > authentication fails because there is no enabled type on the client > which matches any of the server's type. > > Hope this quick explanation was helpful.
That all makes sense. What I'm saying is that, if the client does not explicitly specify the -SecurityTypes parameter, it should honor the types specified on the server, in the order specified on the server. In this case, that would mean preferring Plain authentication. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
