Skip to content

1.2.1
Compare
Choose a tag to compare
@dcommander dcommander released this 30 Jul 00:27
1.2.1
359cb26

Assets

  • turbovnc-1.2.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 1.3.0.

Support

Code Quality: Stable
Current Support Category: EOL

Documentation

User’s Guide for TurboVNC 1.2.1

Release Notes

Significant changes relative to 1.2:

  1. Fixed two regressions introduced in TurboVNC 1.0, one of which prevented older (RFB <= 3.3) VNC viewers from connecting successfully to the TurboVNC Server and the other of which prevented viewers other than TurboVNC and TightVNC from connecting to the TurboVNC Server using no authentication.

  2. Added a new parameter (EncPassword) to the Java TurboVNC Viewer that allows the password to be specified in encrypted ASCII hex.

  3. The toolbar buttons in the Java TurboVNC Viewer that send keystrokes are now disabled when view-only mode is selected.

  4. Enabled the MIT-SCREEN-SAVER X extension in the TurboVNC Server. Modern screen savers don't actually use this extension, but it provides an easy way for applications to query the idle time of the X server.

  5. Fixed a regression introduced in 1.2 beta1 whereby the TurboVNC Viewer desktop shortcut installed with the Linux RPM did not work properly.

  6. Fixed a bug in the Java TurboVNC Viewer's RRE decoder that was causing pixels to be displayed incorrectly.

  7. Pressing F8 (or the chosen menu key) twice in the Java TurboVNC Viewer now sends that keystroke to the VNC server. This emulates the behavior of the X11 viewer.

  8. Added an option to vncserver that allows the output of Xvnc to be redirected to an arbitrary file.

  9. Implemented the X RANDR extension in the TurboVNC Server. The main purpose of this at the moment is to placate applications that check for the extension and refuse to start without it. The extension currently can't be used to change the screen size (that feature will be in TurboVNC 2.0.)

  10. Fixed an issue in the Java TurboVNC Viewer whereby, when a mouse button was pressed, pressing another button or activating the scroll wheel would cause the viewer to send a release event for the first button.

  11. Fixed an issue whereby the X11 TurboVNC Viewer would fail to authenticate if the encrypted password stored in the connection info file started with "00".

  12. Fixed an invalid memory access that occurred in the TurboVNC Server after a viewer disconnected. This had the visible effect of causing an error ("Could not disable TCP corking: Bad file descriptor") to be printed to the TurboVNC Server's log, but it was not known to cause any other issues.

  13. Fixed an issue that prevented clipboard transfer from working properly with applications that request the clipboard selection in a non-ASCII format. This was specifically known to affect rxvt-unicode.

  14. The Windows TurboVNC Viewer should now build properly with Visual Studio 2012.

  15. The "Uninstall TurboVNC" app should once again work on OS X 10.5.

  16. Added two new command-line options to PuTTY, -L4 and -L6. These work just like -L, except that -L4 forces PuTTY to use an IPv4 interface for the client side of the SSH tunnel, and -L6 forces PuTTY to use an IPv6 interface for the client side of the SSH tunnel.

  17. Worked around an issue whereby the Java/Mac TurboVNC Viewer would abort with "InStream max string length exceeded" when connecting to recent versions of the RealVNC Server. This was due to a protocol conflict. Apparently, RealVNC uses pseudo-encoding number -311 for their CursorWithAlpha extension, but TigerVNC uses -311 for ClientRedirect. At least for now, ClientRedirect has been disabled in the Java TurboVNC Viewer by default, but there is a new hidden parameter (ClientRedirect) that can be set to 1 to re-enable it.

  18. Due to an oversight, the 3-button mouse emulation feature in the Windows TurboVNC Viewer was being enabled by default. This has been fixed. 3-button mouse emulation is largely unnecessary with modern systems, and the feature is known to cause issues with certain applications.

Assets 14
Loading