The default behavior, assuming that both client and server were built with TLS support, is that VncAuth will be used by default, but TLSVnc can always be requested by the client, either from the command line or the GUI. If this isn't working, run Xvnc -? on the server and make sure that TLSVnc appears as an available security type.
On 3/8/11 8:53 AM, Robert Goley wrote: > One additional thing. It seems that TLS connections are disabled by > default. Not sure if this is the real default or the result of using a > build without TLS prior to this version. My understanding was that TLS > would be enabled so that VncAuth was default and TLS was available if > requested by the client. Is that the case? ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
