These packages were built with libjpeg-turbo 1.5.1:
http://sourceforge.net/projects/libjpeg-turbo/files/1.5.1/

Packaging changes

A new build of the Linux RPMs and DEBs was uploaded on 2017-04-05 to fix an issue whereby the TurboVNC Viewer JARs delivered via the TurboVNC Server's zero-install Java Web Start interface failed to launch ("com.sun.deploy.net.JARSigningException: Found unsigned entry in resource") with older JRE releases.

Package signatures

To ensure the integrity of the TurboVNC binary packages, the RPM and DEB files and the source tarball are signed using the following key:
http://www.TurboVNC.org/key/VGL-GPG-KEY-1024
http://pgp.mit.edu/pks/lookup?op=get&search=0x6BBEFA1972FEB9CE
and the Windows installers are signed using a code signing certificate.

2.1.1

Significant changes relative to 2.1:

1. Fixed an XML error ("The processing instruction target matching '[xX][mM][lL]' is not allowed" or "Could not parse launch file") that occurred when attempting to launch the Java TurboVNC Viewer using the built-in zero-install Java Web Start feature in the TurboVNC Server. Apparently recent releases of Java did not like the fact that the JNLP file generated by the TurboVNC Server began with an XML comment.

2. Arguments to the vncserver script are now case-insensitive.

3. The TurboVNC Server init.d script was erroneously checking for the existence of ~/.vnc/passwd, even if the permitted and selected security types did not require a VNC password file. The init.d script now invokes vncserver with a new argument (-quiet) that causes vncserver to fail if a VNC password file is required but does not exist.

4. The Java TurboVNC Viewer now supports the rfbTLS security descriptor used by Vino. This should allow the viewer to connect to encrypted Vino sessions using either the TLSVnc or TLSNone security types.

5. The default behavior of the TurboVNC Server is to refuse new non-shared connections if a viewer is already connected. Previously, the server accomplished this by hard-coding the -dontdisconnect argument to Xvnc inside of the vncserver wrapper script. This release of TurboVNC instead makes -dontdisconnect the default in Xvnc and introduces a new Xvnc argument (-disconnect) to reverse the behavior. This new option allows TurboVNC to mimic the behavior of other VNC implementations that disconnect existing viewers when a new non-shared connection is established.

6. Added a new parameter to the Java TurboVNC Viewer (LocalCursor) that, when enabled, causes cursor shape updates to be ignored and the local cursor to always be displayed. This mimics the behavior of the Windows TurboVNC Viewer when "Local cursor shape" is set to "Normal arrow" and "Mouse cursor" is set to "Don't show remote cursor". This option is useful when connecting to broken VNC server implementations that do not properly support server-side cursor rendering or cursor shape updates.

7. Fixed an issue in the Windows TurboVNC Viewer whereby the mouse scroll wheel would stop working if the viewer was moved to a monitor above or to the left of the Windows "main"/"primary" display.

8. Fixed an issue whereby zero-height PutImage requests (issued by XCB) would crash the TurboVNC X server. This was known to affect certain Qt5 applications running under Debian Stretch but may have also affected other applications and platforms.