Download Latest Version c9106887b822e03b20f3a3f29decc0a11d56f0dee0ef47b9d79cf8f1f0499098-filelists.sqlite.bz2 (200.3 kB)
Email in envelope

Get an email when there's a new version of TurboVNC

Home / 2.2.2
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2023-08-23 3.4 kB
turbovnc_2.2.2_i386.deb 2019-05-23 5.0 MB
turbovnc_2.2.2_amd64.deb 2019-05-23 5.1 MB
turbovnc-debuginfo-2.2.2.x86_64.rpm 2019-05-23 10.1 MB
turbovnc-debuginfo-2.2.2.i386.rpm 2019-05-23 9.9 MB
turbovnc-2.2.2.x86_64.rpm 2019-05-23 4.9 MB
turbovnc-2.2.2.tar.gz 2019-05-23 9.0 MB
turbovnc-2.2.2.tar.gz.sig 2019-05-23 65 Bytes
turbovnc-2.2.2.src.rpm 2019-05-23 8.9 MB
turbovnc-2.2.2.i386.rpm 2019-05-23 4.7 MB
turbovnc-2.2.2-jws.zip 2019-05-23 121.1 kB
TurboVNC-2.2.2.dmg 2019-05-23 4.2 MB
TurboVNC-2.2.2-x86.exe 2019-05-23 2.3 MB
TurboVNC-2.2.2-x64.exe 2019-05-23 2.3 MB
Totals: 14 Items   66.6 MB 6

These packages were built with libjpeg-turbo 2.0.2:
https://sourceforge.net/projects/libjpeg-turbo/files/2.0.2/

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:
https://www.TurboVNC.org/key/VGL-GPG-KEY-1024
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xecf01671d05e2a105ff84dc46bbefa1972feb9ce
and the Windows installers and Mac app/package/DMG are signed using a code signing certificate.

2.2.2

Significant changes relative to 2.2.1:

  1. Fixed an error ("javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)") that occurred when attempting to use any of the TLS* security types with the Java TurboVNC Viewer running under Java 7u211, 8u201, 11.0.2, or later.

  2. Fixed an issue in the Java TurboVNC Viewer's built-in SSH client whereby values for the ServerAliveInterval keyword in the OpenSSH config file were interpreted as milliseconds rather than seconds. This caused the SSH connection to fail if the value specified for ServerAliveInterval was too low.

  3. Fixed a regression introduced by 2.2.1[6] that caused constant flickering in the UltraVNC Viewer when it was used with the TurboVNC Server.

  4. Fixed an issue in the TurboVNC Server whereby, if interframe comparison was enabled and the remote desktop was resized to a smaller size, the server would sometimes send a framebuffer update that exceeded the new desktop dimensions. This crashed the UltraVNC Viewer.

  5. Fixed a denial-of-service (DoS) vulnerability in the TurboVNC Server that was exposed when many RFB connections were made to the server and never dropped, thus exceeding the Xvnc process's allotment of file descriptors. When this occurred, it triggered an infinite loop whereby the TurboVNC Server's listener socket handler returned immediately with an EMFILE ("Too many open files") error, but the handler continued to be called by the X.Org code because the incoming RFB connection never succeeded. This infinite loop prevented the TurboVNC session owner from launching any X11 programs in the session (since those require Unix domain socket connections) until one or more of the RFB connections dropped, and the continuous flood of error messages in the session log caused the log to grow by megabytes per second until all available disk space was exhausted. The TurboVNC Server now sets a reasonable RFB connection limit (which can be adjusted using a new Xvnc argument, -maxconnections) and rejects all new connections once this limit has been reached. The upper limit for -maxconnections should be low enough to avoid the aforementioned EMFILE error and infinite loop.

  6. Fixed an issue in the Linux/Un*x TurboVNC Viewer whereby, if multiple buttons on an extended input device (such as a drawing tablet) were pressed or released in rapid succession, some of those button events could accidentally be discarded by the TurboVNC Helper under certain circumstances, leading to a loss of synchronization between the client's and the TurboVNC session's extended input device button state. From the point of view of applications running in the TurboVNC session, the extended input device buttons appeared to stick in the down or up position.

Source: README.md, updated 2023-08-23