http://www.turbovnc.org/DeveloperInfo/PreReleases
(under 2.1 Alpha) Feedback needed. Full support for the VeNCrypt TLS security types is included (and documented) in both the Java/Un*x/Mac viewer and the server (not available in the Windows native viewer yet-- see https://github.com/TurboVNC/turbovnc/issues/8.) The official binaries available on the page above use OpenSSL to implement encryption on the server side, and OpenSSL is dynamically loaded to Xvnc using dlopen()/dlsym() to avoid compatibility issues among various Linux distros. You can also choose to use GnuTLS if you rebuild the server from source (OpenSSL is the default because it's faster.) Please take the feature for a spin and let me know what breaks. Note that the VeNCrypt extensions have been merged into the existing TurboVNC authentication/security framework, so some of the behavior in the server is a bit different now-- "permitted-auth-methods" in the security config file has been replaced by "permitted-security-types", and a "-securitytypes" command-line argument to Xvnc replaces the "-otpauth" and "-pamauth" arguments. There are also new Xvnc arguments that allow an X.509 certificate to be specified. You will want to use the new Java viewer at the same link above when testing the new server. The 2.0 Java viewer has a bug that prevents it from working properly with a server that supports both the TightVNC and VeNCrypt security extensions. DRC ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
