VNC® Personal Edition 4.6 release notes
Introduction
Below are the release notes for version 4.6. You can also read the release notes for versions 4.5.x and earlier. There is also a list of known bugs in version 4.6.
VNC Personal Edition 4.6.3 - released 19th August 2011
- Updated for compatibility with VNC Enterprise Edition 4.6.3.
VNC Personal Edition 4.6.2 - released 11th August 2011
- FIXED: Connections from VNC Viewer to Mac OS X 10.7 (Lion) computers running VNC Enterprise Edition now work as expected.
VNC Personal Edition 4.6.1 - released 8th March 2011
- FIXED: Mouse movement no longer appears jerky or affects performance when connected to Windows host computers.
- FIXED: Re-opening the Chat - VNC Server dialog now retains user names and distinguishing colors.
- FIXED: File transfer no longer occasionally fails due to issues assigning file permissions.
- FIXED: VNC Viewer no longer appears to offer authenticated connections to proxy servers. Note that support for proxy authentication may be the subject of a future release.
- FIXED: Changing the color quality of a host computer desktop running VNC Server in Service Mode with the Mirror Driver enabled (the default behavior) no longer blanks, or stops updating, the display.
- FIXED: Setting the VNC Server in Service Mode
LogandLogFileparameters now successfully logs to a file in a privileged directory.
VNC Personal Edition 4.6 - released 20th December 2010
- NEW: Full Windows 7 support.
- NEW: Connections can be secured end-to-end using 256-bit AES encryption.
- NEW:
JPEGandJRLEencodings for the VNC Viewerpreferredencodingparameter compress pictures more efficiently for improved performance over low bandwidth connections. - NEW:
Zlibencoding for the VNC Viewerpreferredencodingparameter improves the performance of connections to Mac OS X computers running Apple Remote Desktop/Remote Management. - NEW: Executable files are Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR)-enabled for improved security on appropriate operating systems.
- NEW: Separate private keys are automatically generated when VNC Viewer and VNC Server start.
- NEW: Multiple host computers can be specified at the VNC Viewer command line, and connections attempted in turn until one succeeds. Or all can be established at once using the
connectinparallelparameter. - NEW: Alpha-blended cursors are supported.
- NEW: VNC Server connection notification messages can be turned off.
- NEW: VNC Server notifies when chat messages are received if the Chat - VNC Server dialog is minimized.
- Streamlined file transfer mechanism and user interface.
- VNC Personal Edition no longer supports Itanium processors.
- VNC Server can now be restricted to IPv6 network addresses for the host computer by setting the
InTransportsparameter to justIPv6. In addition, invalid values for this parameter now prevent connections. - Corrupt or missing private keys can no longer be regenerated from the UI.
- VNC Server for Windows in User Mode now displays a black screen when the host computer's desktop cannot be accessed, instead of terminating connections (for example, when a UAC prompt is displayed, or when the host computer is locked).
- VNC Server now warns if a password specified for the
VNC Passwordauthentication mechanism is shorter than six characters. - Blacklisting now only affects client computers whose users fail to authenticate, enabling utilities such as
pingto work. - Many dialogs and message windows have new and more consistent titles.
- Printing formats have changed, and dependencies removed. This means VNC Viewer 4.6 cannot print host computer files from VNC Server 4.5 for UNIX/Linux or Mac OS X. See also the bug fix below.
- FIXED: Printing formats have changed. This means Standalone VNC Viewer 4.6 can now print host computer files from VNC Server 4.6 for UNIX/Linux or Mac OS X (but not VNC Server 4.5).
- FIXED: Command line parameters specified when starting VNC Viewer are now inherited (when a new connection is established using the New Connection toolbar button, for example).
- FIXED: Command line parameters specified when starting Listening VNC Viewer are now respected.
