Skip to content

2.2.1
Compare
Choose a tag to compare
@dcommander dcommander released this 03 Jan 00:27
2.2.1
f634c58

Assets

  • turbovnc-2.2.1.tar.gz is the official source tarball for this release. The automatically generated "Source code" assets are not supported.
  • Refer to https://TurboVNC.org/Downloads/DigitalSignatures for information regarding the methods used to sign the files in this release and instructions for verifying the signatures.
  • The binary packages were built with libjpeg-turbo 2.0.1.

Support

Code Quality: Stable
Current Support Category: Extended

Documentation

User’s Guide for TurboVNC 2.2.1

Release Notes

Significant changes relative to 2.2:

  1. The standalone Mac TurboVNC Viewer app will now use the JRE pointed to by the JAVA_HOME environment variable, if that variable is defined. This facilitates using the viewer with Java 11, which doesn't provide a separate JRE and thus doesn't install anything under /Library/Internet Plug-Ins/JavaAppletPlugin.plugin (the directory in which the Mac TurboVNC Viewer app launcher normally looks for a JRE.)

  2. The Windows TurboVNC Viewer packages no longer include a custom build of PuTTY. An optimized version of PuTTY 0.60 was originally included in TurboVNC 0.4/Sun Shared Visualization 1.1 because, at the time, the stock version of PuTTY was slow, and installing OpenSSH generally required Cygwin. The custom build of PuTTY was retained in TurboVNC 1.2, because few Windows SSH implementations had proper IPv6 support at the time. However, in 2018, numerous Windows SSH clients will work properly with the TurboVNC Viewer, and generally with better performance than our custom build of PuTTY.

  3. Fixed an issue in the vncserver script whereby generating an initial one-time password (OTP) would fail if X11 TCP connections were disabled (which is now the default, because of 2.2 beta1[8]) and the hostname of the TurboVNC host resolved to its external IP address rather than to its local IP address.

  4. The Java TurboVNC Viewer will now display all informational messages and warnings from its built-in SSH client whenever the logging level is >= 110.

  5. The built-in SSH client in the Java TurboVNC Viewer has been improved in the following ways:

    • The SSH client will now prompt for an SSH key passphrase if one is required but has not been specified using the SSHKeyPass parameter. This emulates the behavior of OpenSSH.
    • The SSH Password dialog will no longer be displayed unless SSH password authentication is necessary. Previously, the dialog was displayed even if the hostname was invalid.
    • Closing the SSH Password dialog will now immediately cancel SSH authentication.
    • The SSH client will now automatically read and process the OpenSSH configuration file stored in ~/.ssh/config (or the location specified in the SSHConfig parameter), if the file exists. Parameters read from the OpenSSH configuration file will take precedence over any TurboVNC Viewer parameters.
    • A new Java system property (turbovnc.sshauth) can be used to enable or disable SSH authentication methods, as well as to specify their preferred order.

  6. Fixed a race condition in the TurboVNC Server that, under rare circumstances, caused the TurboVNC Viewer to incorrectly assume that the server did not support remote desktop resizing.

  7. Fixed an issue in the vncserver script whereby changing the value of $vncUserDir in turbovncserver.conf did not change the default locations of the VNC password file, the X.509 certificate file, and the X.509 private key file. The script now defers setting the default locations of those files until after turbovncserver.conf is read, and the script now allows the locations of all three files to be specified in turbovncserver.conf.

  8. The vncserver script now allows VirtualGL to be enabled using the turbovncserver.conf file.

  9. The vncserver script now allows the window manager startup script to be specified using a new command-line option (-wm) or turbovncserver.conf variable ($wm.) This is useful when starting TurboVNC sessions at boot time, and for other situations in which setting the TVNC_WM environment variable is not possible.

  10. The TurboVNC Server now properly handles installations in which the system-wide TurboVNC configuration file (turbovncserver.conf) and security configuration file (turbovncserver-security.conf) are located in a directory other than /etc.

  11. Introduced a new turbovncserver.conf variable ($serverArgs) that can be used to specify additional arguments for Xvnc. This allows any TurboVNC Server option to be enabled or disabled on a system-wide or per-user basis, even if that option has no corresponding turbovncserver.conf variable.

  12. Fixed an issue in the Windows/Java and Un*x TurboVNC Viewers whereby, when pressing and releasing both the left and right locations of a particular modifier key (Shift, Ctrl, Alt, etc.), only one of the key releases was sent to the VNC server. Fixed a similar issue in the Mac TurboVNC Viewer under Java 11 whereby, when pressing and releasing both the left and right Alt keys in the same order, a left Alt key press and an AltGr key release (or vice versa) were sent to the VNC server.

  13. Fixed a segfault in the TurboVNC Server that occurred, under rare circumstances, when a viewer disconnected.

  14. Fixed an issue in the TurboVNC Server, introduced by 2.2 beta1[11], that prevented client-to-server clipboard transfers from working properly with some Qt applications.

Assets 15
Loading