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 / 3.0
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2023-08-23 3.6 kB
turbovnc-debuginfo-3.0.x86_64.rpm 2022-09-13 9.0 MB
turbovnc-debuginfo-3.0.i386.rpm 2022-09-13 8.8 MB
turbovnc-3.0.x86_64.rpm 2022-09-13 41.1 MB
turbovnc-3.0.src.rpm 2022-09-13 8.7 MB
turbovnc-3.0.i386.rpm 2022-09-13 2.9 MB
turbovnc-3.0.aarch64.rpm 2022-09-13 39.6 MB
turbovnc_3.0_i386.deb 2022-05-03 3.5 MB
turbovnc_3.0_arm64.deb 2022-05-03 42.2 MB
turbovnc_3.0_amd64.deb 2022-05-03 43.8 MB
turbovnc-3.0.tar.gz.sig 2022-05-03 543 Bytes
turbovnc-3.0.tar.gz 2022-05-03 8.7 MB
TurboVNC-3.0.dmg 2022-05-03 38.3 MB
TurboVNC-3.0-x86.exe 2022-05-03 38.9 MB
TurboVNC-3.0-x64.exe 2022-05-03 41.0 MB
Totals: 15 Items   326.3 MB 21

These packages were built with libjpeg-turbo 2.1.3:
https://sourceforge.net/projects/libjpeg-turbo/files/2.1.3/
and Adoptium OpenJDK 11.0.15_8:
https://github.com/adoptium/temurin11-binaries/releases/tag/jdk-11.0.15%2B10
(Adoptium OpenJDK 11.0.14.1 used for 32-bit Windows)
https://github.com/adoptium/temurin11-binaries/releases/download/jdk-11.0.14.1%2B1

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
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xae1a7ba4efff9a9987e1474c4baccab36e7fe9a1
and the Windows installers and Mac app/package/DMG are signed using a code signing certificate.

Packaging changes

  • A Linux/AArch64 RPM and DEB package are now provided.
  • New RPMs with SHA-256 digests were uploaded on 2022-09-12. This fixes an issue whereby the RPM signatures could not be successfully verified on Red Hat Enterprise Linux 9 when using its default crypto policy, which restricts the use of the SHA-1 algorithm.

3.0

Significant changes relative to 3.0 beta1:

  1. Fixed an issue in the TurboVNC Viewer whereby scroll wheel events were transmitted to the VNC Server with incorrect coordinates if desktop scaling was enabled.

  2. The simple web server for noVNC (part of the TurboVNC Server) now supports Python 3, and the official TurboVNC packages now require Python 3. The TurboVNC Server must be built with CMake 3.12 or later in order for the simple web server to use Python 3.

  3. Fixed an error ("couldn't find '*/bin/webserver'") that occurred when attempting to run the vncserver script if TurboVNC was built without the optional noVNC web server.

  4. Fixed a regression in the TurboVNC Viewer whereby specifying the User or SendLocalUserName parameter did not automatically disable security types that do not use the Unix Login and Plain authentication schemes.

  5. The RPM package generated by the TurboVNC build/packaging system now includes post-install and pre-uninstall scriplets that configure/unconfigure the TurboVNC Server init.d script to run in the unconfined_service_t SELinux domain rather than the initrc_exec_t SELinux domain. This fixes an issue whereby either Xvnc or the window manager failed to launch when attempting to start a TurboVNC session from the TurboVNC Server init.d script on recent Red Hat Enterprise Linux (and derivative), Fedora, and SuSE releases.

  6. The TurboVNC Viewer now overrides Java's default choice of high DPI scaling algorithms on Windows. This eliminates visual artifacts when using fractional display scaling factors such as 125%.

  7. The vncserver script now sets the VGL_PROBEGLX environment variable to 0. This prevents VirtualGL from probing the TurboVNC X Server for stereo-capable X visuals. (Such visuals will never exist in an X proxy such as TurboVNC.) On systems that support libglvnd, probing for stereo-capable visuals caused the Mesa GLX vendor library to be loaded into the 3D application process, which led to interaction issues with certain commercial 3D applications that provide their own Mesa back ends.

  8. Fixed an error ("Server TLS ERROR: Could not load libssl") that occurred when attempting to use TLS encryption with the TurboVNC Server (built with TVNC_DLOPENSSL=1, which is the default) running on a TurboVNC host with OpenSSL 3.

  9. The TurboVNC Server is now based on xorg-xserver 1.20.14, which fixes several minor X server bugs.

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