Significant changes since 1.2:
 Fixed two regressions introduced in TurboVNC 1.0, one of which
prevented older (RFB <= 3.3) VNC clients from connecting successfully to
the TurboVNC Server and the other of which prevented clients other than
TurboVNC and TightVNC from connecting to the TurboVNC Server using no
 Added a new parameter (EncPassword) to the Java TurboVNC Viewer that
allows the password to be specified in encrypted ASCII hex.
 The toolbar buttons in the Java TurboVNC Viewer that send keystrokes
are now disabled when view-only mode is selected.
 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.
 Fixed a regression introduced in 1.2 beta1 whereby the TurboVNC
Viewer desktop shortcut installed with the Linux RPM did not work properly.
 Fixed a bug in the Java TurboVNC Viewer's RRE decoder that was
causing pixels to be displayed incorrectly.
 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.
 Added an option to vncserver that allows the output of Xvnc to be
redirected to an arbitrary file.
 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
 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.
 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".
 Fixed an invalid memory access that occurred in the TurboVNC Server
after a client 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
 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.
 The Windows TurboVNC Viewer should now build properly with Visual
 The "Uninstall TurboVNC" app should once again work on 32-bit OS X
 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.
 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.
 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.