The current binaries have all of the modifications you describe (VeNCrypt no longer needs to be specified, the server's security type order is preferred, and VncAuth is at the top of the server's security type list.)
On 3/1/11 11:48 AM, Robert Goley wrote: > My understanding is that they were going to change the auth code so that > it defaulted to using VeNCrypt so that you would no longer have to > specify it on the command line. You would however have to set the > method priority. The method priority would default to VncAuth for > compatibility. I do not know if that was completed or is in the current > binaries that DRC built. I am running the same binaries and I am still > specifying in the old manner. I have not tested the short form using > them. I was not sure if that work was completed yet. > > Again this is my understanding from following that thread. If anything > in my 2 cents above is incorrect, please jump in let me know. > > > Robert ------------------------------------------------------------------------------ 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
