Assets
- turbovnc-3.0.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.1.4 and Adoptium OpenJDK 11.0.16+8.
Packaging Changes
- A Mac package/DMG for Apple silicon (Arm) CPUs is now provided.
Support
Code Quality: Stable
Current Support Category: Extended
Documentation
User’s Guide for TurboVNC 3.0.1
Release Notes
Significant changes relative to 3.0:
-
Fixed an error ("JRELoadError") that occurred when attempting to use the Mac TurboVNC Viewer app with a custom JRE based on OpenJDK 17.
-
The TurboVNC Viewer's built-in SSH client now supports the OpenSSH v1 private key format. This fixes an "invalid privatekey" error that occurred when attempting to use a private key generated by a recent version of OpenSSH with the TurboVNC Viewer without
ssh-agentor Pageant. -
The TurboVNC Viewer's built-in SSH client now supports the
rsa-sha2-256andrsa-sha2-512signature schemes (RSA keys with, respectively, the SHA-256 and SHA-512 hash algorithms.) This improves security and compatibility with recent OpenSSH releases. (OpenSSH v8.8 no longer supports thessh-rsasignature scheme by default, sincessh-rsauses the now-defeated SHA-1 hash algorithm.) The built-in SSH client now also supports thePubkeyAcceptedAlgorithmskeyword in OpenSSH config files, which can be used to disable specific signature schemes that both the client and server support. -
The TurboVNC Server and Viewer now truncate both incoming and outgoing clipboard updates to the number of bytes specified by the
-maxclipboardXvnc argument or theMaxClipboardTurboVNC Viewer parameter. Previously the server only truncated incoming clipboard updates, and the viewer truncated outgoing clipboard updates while ignoring incoming clipboard updates larger than 256 kB. -
Fixed an issue in the TurboVNC Viewer whereby specifying a key other than a function key (
F1throughF12) using theMenuKeyparameter caused "F1" to be selected in the "Menu key" combo box in the TurboVNC Viewer Options dialog. -
Fixed an error ("Security type not supported") that occurred when attempting to connect to a TurboVNC session using the TurboVNC Session Manager if the "VNC" security type was disabled in the TurboVNC Viewer (by way of the
SecurityTypes,SendLocalUserName, orUserparameter or a corresponding check box in the TurboVNC Viewer Options dialog) and theSessMgrAutoparameter was enabled. -
The TurboVNC Viewer now builds and runs on Macs with Apple silicon CPUs.