Skip to content

3.0.1

Compare
Choose a tag to compare
@dcommander dcommander released this 15 Aug 16:59
· 291 commits to main since this release

Assets

Packaging Changes

  • A Mac package/DMG for Apple silicon (Arm) CPUs is now provided.

Support

Code Quality: Stable
Current Support Category: Maintenance

Documentation

User’s Guide for TurboVNC 3.0.1

Release Notes

Significant changes relative to 3.0:

  1. Fixed an error ("JRELoadError") that occurred when attempting to use the Mac TurboVNC Viewer app with a custom JRE based on OpenJDK 17.

  2. 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-agent or Pageant.

  3. The TurboVNC Viewer's built-in SSH client now supports the rsa-sha2-256 and rsa-sha2-512 signature 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 the ssh-rsa signature scheme by default, since ssh-rsa uses the now-defeated SHA-1 hash algorithm.) The built-in SSH client now also supports the PubkeyAcceptedAlgorithms keyword in OpenSSH config files, which can be used to disable specific signature schemes that both the client and server support.

  4. The TurboVNC Server and Viewer now truncate both incoming and outgoing clipboard updates to the number of bytes specified by the -maxclipboard Xvnc argument or the MaxClipboard TurboVNC 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.

  5. Fixed an issue in the TurboVNC Viewer whereby specifying a key other than a function key (F1 through F12) using the MenuKey parameter caused "F1" to be selected in the "Menu key" combo box in the TurboVNC Viewer Options dialog.

  6. 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, or User parameter or a corresponding check box in the TurboVNC Viewer Options dialog) and the SessMgrAuto parameter was enabled.

  7. The TurboVNC Viewer now builds and runs on Macs with Apple silicon CPUs.