On Thu, Feb 10, 2011 at 03:46:17PM -0600, DRC wrote: > On 2/10/11 3:35 PM, Martin Koegler wrote: > >> We could always port over an authentication method that supports > >> username/password without the full encryption framework. I don't have > >> any objections to that. > > > > It's already present in the SVN version, but not enabled in the > > default security type list: > > > > Plain sends a user + password string to the server. > > That worked. Thanks! I'll say again that all of this really needs to > be documented (but I'm not volunteering.)
We have: * VeNcrypt - in my option this should be always at position 1 (see my other mail for reasons) * None - no encryption/no authentification * VNCAuth - no encrpytion/VNC Authentification * Plain - no encryption/send user+password * TLSNone - anonymous TLS encryption / no authentification * X509None - X509 based encryption / no authentification * TLSVnc = TLSNone + VNCAuth * X509Vnc = X509None + VNCAuth * TLSPlain = TLSNone + Plain * X509Plain = X509None + Plain Options at the server: * VNCAuth has an password file option [eg. PasswordFile] * Plain has a user list option (PlainUsers) * X509None (+combinations) need x509cert and x509key All other security types have no options. Options at the client: * X509None (+combinations): x509ca + x509crl * VNCAuth: passing the password via a file is possible All other security types have no options. Regards, Martin Kögler ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
