TurboVNC: baixar versions anteriors

Significant changes relative to 3.3:
1. The simple web server for noVNC (part of the TurboVNC Server) now supports Python 3.12 and later when using TLS encryption.
2. The TurboVNC Viewer now supports 3-button mouse emulation, which addresses a feature regression relative to the native Windows TurboVNC 2.2.x Viewer. New parameters (Emulate3, Emulate3Fuzz, Emulate3Timeout, and Emulate3Modifiers) and a new check box in the TurboVNC Viewer Options dialog can be used to enable and configure 3-button mouse emulation. Emulate3, Emulate3Fuzz, and Emulate3Timeout work identically to the corresponding command-line options in the native Windows TurboVNC 2.2.x Viewer, enabling middle mouse button emulation with a left and right mouse button chord. Emulate3Modifiers enables middle mouse button emulation with the left mouse button and a specified combination of modifier keys.
3. The optional TurboVNC Server init.d script for Linux has been improved in the following ways:
- The script has been reimplemented as a systemd service, which extends compatibility to Fedora 45 and later, SUSE 16 and later, and other Linux distributions that no longer translate SysV init scripts. (systemd-sysv-generator was removed in systemd v260.) This also fixes a dependency error when installing an official TurboVNC RPM package on SUSE 16.
- To match the behavior of the official RPM packages, the official TurboVNC DEB packages now configure the TurboVNC Server service when the package is freshly installed and unconfigure it when the package is removed.
- The official TurboVNC RPM and DEB packages now invoke systemctl preset tvncserver when the package is freshly installed, which allows system administrators to use a systemd preset file to specify that the TurboVNC Server service should be enabled by default. (Previously, the TurboVNC Server service was always enabled by default when an official TurboVNC RPM package was freshly installed.)
- The TurboVNC Server service is no longer restarted when an official TurboVNC RPM package is upgraded. This allows system administrators to hot patch systems with active TurboVNC sessions.
4. Fixed an issue whereby the TurboVNC Viewer became unresponsive if the TigerVNC Server intentionally disconnected a TLS-encrypted connection.
5. Fixed an issue in the TurboVNC Viewer whereby hotkey sequences could be triggered with any superset of the modifier keys specified in the HotkeyModifiers parameter (for example, Ctrl-Alt-Meta if Ctrl-Meta was specified.)

Significant changes relative to 3.3 beta2:
1. For compatibility with OpenSSH, the TurboVNC Viewer's built-in SSH client now disables multi-hop/multi-level SSH tunneling if a case-insensitive argument of none is specified for the ProxyJump OpenSSH config file keyword. This is useful in conjunction with wildcard Host entries.
2. The TurboVNC Viewer's built-in SSH client now prints an SSH debugging message, rather than throwing a fatal error, if it cannot parse an entry in the SSH known hosts file. This mimics the behavior of OpenSSH.
3. The TurboVNC Server now includes various security fixes (CVE-2025-26594, CVE-2025-26595, CVE-2025-26596, CVE-2025-26597, CVE-2025-26598, CVE-2025-26599, CVE-2025-26600, CVE-2025-26601, CVE-2025-49175, CVE-2025-49176, CVE-2025-49178, CVE-2025-49179, CVE-2025-49180, CVE-2025-62229, CVE-2025-62230, and CVE-2025-62231) from the xorg-server 21.1.x code base.

Significant changes relative to 3.2:
1. Fixed an issue in the TurboVNC Viewer whereby the "Default Window Size/Position" feature did not work properly in full-screen mode if TVNC_SINGLESCREEN/turbovnc.singlescreen was enabled.
2. When using server-side key mapping, the Windows TurboVNC Viewer now works around an issue whereby the operating system does not send a key release event to applications if one of the Shift keys is released while the other Shift key remains pressed. 2.2.4[1] worked around this issue when using client-side key mapping, but due to an oversight, the server-side key mapping feature introduced in 3.1 beta1[4] did not include the same workaround.
3. The default X startup script (xstartup.turbovnc) now assigns the same priority to session desktop files located in /usr/share/wayland-sessions and /usr/share/xsessions. This prevents an issue on Fedora 40 and later whereby, if GNOME and Xfce or MATE were installed but the (now optional) gnome-session-xsession package was not installed, TurboVNC used Xfce or MATE as the default window manager rather than GNOME.

Significant changes relative to 3.2 beta1:
1. Fixed a regression introduced by 3.0.3[7] that, under rare circumstances if automatic desktop resizing was enabled, caused the viewer to deadlock while resizing its window in response to a remote desktop size change.
2. Fixed an issue whereby the TurboVNC Viewer threw an IllegalComponentStateException if "Remote desktop size" was changed to "Auto" in the TurboVNC Viewer Options dialog while the viewer was actively receiving framebuffer updates from a VNC server.
3. Fixed an issue whereby the "Reset all options to defaults" button in the TurboVNC Viewer Options dialog did not take into account the values specified in ~/.vnc/default.turbovnc.
4. The TurboVNC Viewer now works around an issue with recent versions of GNOME that caused erratic automatic desktop resizing behavior.
5. The default X startup script (xstartup.turbovnc) now looks in both /usr/share/xsessions and /usr/share/wayland-sessions for a session desktop file corresponding to the specified window manager. This works around an issue whereby the GNOME Classic window manager could not be used with the TurboVNC Server on Fedora 40 and later.
6. The default X startup script (xstartup.turbovnc) now attempts to launch MATE or Xfce (in that order) if no window manager is specified and a GNOME session desktop file cannot be found. This fixes a regression introduced by 3.2 beta1[4] whereby the default X startup script no longer launched the default window manager on Ubuntu MATE or Xubuntu if no window manager was specified.
7. The "Clear the list of saved connections" button in the "Global" tab of the TurboVNC Viewer Options dialog now clears only the connection history. A separate button has been added for clearing saved per-host options.

Significant changes relative to 3.1.3:
1. Fixed an issue whereby the TurboVNC Viewer threw a NullPointerException if a user clicked the "Connect" button in the New TurboVNC Connection dialog after entering an SSH username with a blank VNC host into the "VNC server" field.
2. To better emulate the behavior of OpenSSH, the TurboVNC Viewer's built-in SSH client now allows the value of the SSHPort parameter, if specified on the command line or in a connection info file, to override any SSH ports specified in the OpenSSH config file.
3. The TurboVNC Server now includes various security fixes (CVE-2023-5367, CVE-2023-6377, CVE-2023-6478, CVE-2023-6816, CVE-2024-0229, CVE-2024-0408, CVE-2024-9632, CVE-2024-21885, CVE-2024-21886, CVE-2024-31080, CVE-2024-31081, and CVE-2024-31083) from the xorg-server 21.1.x code base.
4. Worked around an issue whereby recent versions of GNOME failed to launch in a TurboVNC session if the initial resolution of any of the screens in the session matched one of the default X RandR modes.
5. Fixed an issue in the Mac TurboVNC Viewer whereby the viewer window did not display a vertical scrollbar, and the horizontal scrollbar was incorrectly sized, if multi-screen spanning was enabled, the scaled remote desktop was larger than the viewer window, and "Displays have separate Spaces" was enabled in the system settings.
6. The Windows TurboVNC Viewer now sends Alt-F4 keystrokes to the VNC server if keyboard grabbing is enabled.
7. Fixed a regression introduced by 3.1.2[2] that caused the Mac and Windows TurboVNC Viewers to incorrectly interpret Shift + vertical scroll wheel events as horizontal scroll wheel events.
8. Fixed an issue whereby the TurboVNC Viewer's built-in SSH client threw a NullPointerException if a cipher algorithm supported by the SSH server but not by the SSH client was specified using the Ciphers OpenSSH config file keyword.
9. Fixed an issue in the TurboVNC Viewer's built-in SSH client whereby the SSH connection timeout specified using the ConnectTimeout OpenSSH config file keyword was interpreted as milliseconds rather than seconds. This caused the SSH connection to fail if the timeout was too low.
10. Fixed a regression introduced by 3.1 beta1[3] whereby the value of the TurboVNC Viewer's Subsampling parameter, if specified using the Samp alias, did not override per-host options that were previously saved by the TurboVNC Viewer Options dialog.

Significant changes relative to 3.1.2:
1. Added a new Xvnc command-line option (-noserverkeymap) that can be used to disable the server-side key mapping feature introduced in 3.1 beta1[4].
2. Added a new Xvnc command-line option (-syslog) that can be used to redirect all TurboVNC Server and X.org errors, warnings, and messages to the system log.
3. Fixed a regression introduced by 2.2 beta1[7] that prevented the TurboVNC Server from being used as an inetd service.
4. The "Tight Encoding Without Zlib" RFB extension, which was used unofficially by the Lossless Tight encoding method since TurboVNC v0.5, has been officially registered with IANA as an RFB pseudo-encoding. The TurboVNC Viewer now advertises support for the pseudo-encoding. (The next major release of the TurboVNC Server will forego using the extension unless the VNC viewer advertises support for it.)
5. Fixed an issue in the TurboVNC Viewer's built-in SSH client whereby the ssh-rsa and rsa-sha2-512 signature schemes could not be used unless they were specified as the first argument for the HostKeyAlgorithms OpenSSH config file keyword or the server did not support rsa-sha2-256.
6. Fixed an error ("ZlibInStream: inflate failed") that occurred in the TurboVNC Viewer when it attempted to receive a clipboard update from QEMU's VNC server.
7. Fixed a denial-of-service (DoS) vulnerability in the TurboVNC Server, introduced by 3.0 beta1[20], that triggered an infinite loop in the server's automatic WebSocket detection code if an ill-behaved client sent 3 or fewer bytes of data immediately after connecting. Certain versions of Apache Guacamole were known to trigger this issue sporadically.
8. The TurboVNC Viewer now works around an issue that prevented keyboard grabbing from working when running the viewer in a GNOME/Wayland session.