On 2015-05-08, 4.0.3.2-20150508 was released with the following changes:
- Windows: Update bundled VcXsrv from 1.15.2.5 (X2Go/Arctica Build) to 1.15.2.6 (X2Go/Arctica Build) The differences relevant to X2Go are: + CVE-2015-3418 was fixed in VcXsrv itself + Font files no longer differ in each build due to timestamp differences - Windows: Update libssh from 0.6.4 to 0.6.5 (while maintaining Pageant support). This fixes CVE-2015-3146.
As with most vulnerabilities in 3rd party software, the X2Go project has not done an analysis of whether X2Go Client was actually affected by these vulnerabilities. However, as a precaution, we strongly encourage all users to update.
On 2015-03-29, 4.0.3.2-20150329 was released with the following changes:
- Windows: Update bundled VcXsrv from 1.15.2.4-xp+vc2013+x2go1 to 1.15.2.5 (X2Go/Arctica Build) The differences relevant to X2Go are: + VcXsrv's bundled version of openssl was updated from 1.0.1k to 1.0.1m (fixes the multiple CVEs announced on 2015-03-19) + VcXsrv's bundled version of libXfont was updated from 1.4.8 to 1.4.9 (Fixes CVE-2015-1802 through CVE-2015-1804) - Windows: Update bundled Win32 OpenSSL from 1.0.1L to 1.0.1m, which fixes the multiple CVEs announced on 2015-03-19. - Windows: Update bundled PuTTY from 0.63 to 0.64. In addition to other changes, CVE-2015-2157 has been fixed. - Windows: Update bundled Cygwin openssl from 1.0.1k-1 to 1.0.2a-1. This update fixes the multiple CVEs announced on 2015-03-19
As with most vulnerabilities in 3rd party software, the X2Go project has not done an analysis of whether X2Go Client was actually affected by these vulnerabilities. However, as a precaution, we strongly encourage all users to update.
On 2015-03-01, 4.0.3.2-20150301 was released with the following changes:
As with most vulnerabilities in 3rd party software, the X2Go project has not done an analysis of whether X2Go Client was actually affected by these vulnerabilities. However, as a precaution, we strongly encourage all users to update.
On 2015-02-25, 4.0.3.2-20150224 was released with the following changes:
As with most vulnerabilities in 3rd party software, the X2Go project has not done an analysis of whether X2Go Client was actually affected by these vulnerabilities. However, as a precaution, we strongly encourage all users to update.
None.
All builds with version “4.0.3.2-20150508” in their filename are current.
The regular build, x2goclient-4.0.3.2-20150508-setup.exe, is available under this folder:
A debug build, x2goclient-4.0.3.2-20150508-debug-setup.exe, is also available under the folder listed below. If you experience a bug and would like to assist with debugging it, this build is for you.
The regular builds, x2goclient-4.0.3.2-20150219-setup.exe through x2goclient-4.0.3.2-20150329-setup.exe, are available under these folders:
The debug builds, x2goclient-4.0.3.2-20150219-debug-setup.exe through x2goclient-4.0.3.2-20150329-setup.exe, are also available under these folders. If you experience a bug and would like to assist with debugging it, these builds are for you.
X2Go Client is currently only released as a 32-bit x86 build. Both 32-bit x86 and 64-bit x86 versions of Windows are supported via this build.
These versions of Windows without the latest (specified) service pack may be compatible, but are rarely (if ever) tested. They are not officially supported.
Corresponding server versions of Windows are also supported, but receive minimal testing:
Any incompatibility or bug with a specific version of Windows should be reported via our bug-tracker.
See this page:
None
bug 611 The server cannot be added to the known_hosts file (and thus you cannot connect to the server) when both of these conditions are met: 1. Your Windows username has non-English characters. 2 Those characters are in a different language than the Windows “system locale”.
TODO: List more bugs