On 2/10/11 4:00 PM, Martin Koegler wrote: > Please don't mix up Encryption with VeNCrypt. VeNCrypt consists of two > parts: > > 1) An extended chooser, which has enough available security type > numbers even for every hobby developer. > > 2) New security types (TLS encryption with/without certificates, > Username/Password authentification + various combinations also > reusing the classic security types).
OK, but am I correct in asserting that, in TigerVNC, as it's currently implemented, there is no way to build VeNCrypt without encryption? For now, I just want encryption to be disabled by default, because it's so slow. Longer term, it would be nice to have the ability to build TigerVNC with only the authentication extensions and not require GnuTLS to do so. > Side node: In my option, it would be the best, to let the VeNCrypt > security type vanish for our users (by putting it automatically as > first element to the list of enabled security types) - so enabling it > by default as done for the tight security type. This still works, even > if the user only enables VNCAuth/None and/or communicates with a > non-VenCrypt capable VNC implementation. I have no objection to that, as long as VncAuth is second on the default list, that is, as long as encryption isn't the out-of-box default when you run Xvnc and vncviewer with no arguments. ------------------------------------------------------------------------------ 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
