x2go-commits April 2014

x2go-commits@lists.x2go.org

3 participants
183 discussions

[x2goserver] branch master updated (35d80de -> ae9da46)
by git-admin＠x2go.org 27 Apr '14

27 Apr '14

This is an automated email from the git hooks/post-receive script. x2go pushed a change to branch master in repository x2goserver. from 35d80de Give thanks to Eugene San for the last commit. new ae9da46 Add tunneling port allocation for TeleKinesis framework. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: X2Go/Server/DB.pm | 16 +++++---- X2Go/Server/DB/PostgreSQL.pm | 25 +++++++++---- X2Go/Server/DB/SQLite3.pm | 31 +++++++++++----- X2Go/Utils.pm | 6 ++++ debian/changelog | 1 + debian/control | 1 + x2goserver-common/etc/x2goserver.conf | 5 +++ x2goserver.spec | 1 + x2goserver/bin/x2goresume-session | 36 ++++++++++++++++--- x2goserver/bin/x2gostartagent | 20 +++++++++-- x2goserver/lib/x2gocreatesession | 4 ++- x2goserver/lib/x2goresume | 5 +-- x2goserver/sbin/x2godbadmin | 64 ++++++++++++++++++++++++++++++--- 13 files changed, 179 insertions(+), 36 deletions(-) -- Alioth's /srv/git/_hooks_/post-receive-email on /srv/git/code.x2go.org/x2goserver.git

1 1

[x2goserver] branch telekinesis updated (80b0986 -> 88f7403)
by git-admin＠x2go.org 27 Apr '14

27 Apr '14

This is an automated email from the git hooks/post-receive script. x2go pushed a change to branch telekinesis in repository x2goserver. from 80b0986 intermediate commit new 88f7403 finalize teki integration The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: X2Go/Server/DB.pm | 16 ++++++++++------ X2Go/Server/DB/SQLite3.pm | 12 ++++++------ X2Go/Utils.pm | 6 ++++++ x2goserver/bin/x2gostartagent | 4 ++-- 4 files changed, 24 insertions(+), 14 deletions(-) -- Alioth's /srv/git/_hooks_/post-receive-email on /srv/git/code.x2go.org/x2goserver.git

1 1

page changed: doc:release-notes-mswin:x2goclient-4.0.2.0
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:56 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0?re… New Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0 Edit Summary: [Windows-Specific Bug Fixes] typo User : mikedep333 @@ -78,12 +78,12 @@ *Fix compatibility with PulseAudio 3.0 & later through new cookie handling. (Fixes: #422) *The regular build X2Go Client now includes a fix for bug #363 (choppy audio in Flash Player). Users no longer need to install an "interims" build for that a fix. The following bugfixes are not mentioned in the regular release notes. (They are not mentioned in the regular release notes because they do not consist of fixes to X2GoClient's source code, only to the dependencies bundled.): - *CVE-2014-0160 "Heartbleed" vulnerability (Note: X2Go Client was only affected by the heartbleed vulnerability when connecting to a an X2Go session broker over HTTPS. Even though X2Go Client uses libssh and cygwin's openssh, which both in turn use openssl, they were never affected because the SSH protocol does not contain the SSL heartbeat. For more info on why SSH implementations are not affected, read [[https://access.redhat.com/site/solutions/786603|Red hat's solution article.]]. The only difference between that solution article and X2Go Client is that the vulnerable library file is ssleay32.dll and the non-affected library files are both libeay32.dll and cygcrypto-1.0.0.dll .) + *CVE-2014-0160 "Heartbleed" vulnerability (Note: X2Go Client was only affected by the heartbleed vulnerability when connecting to a an X2Go session broker over HTTPS. Even though X2Go Client uses libssh and cygwin's openssh, which both in turn use openssl, they were never affected because the SSH protocol does not contain the SSL heartbeat. For more info on why SSH implementations are not affected, read [[https://access.redhat.com/site/solutions/786603|Red hat's solution article]]. The only difference between that solution article and X2Go Client is that the vulnerable library file is ssleay32.dll and the non-affected library files are both libeay32.dll and cygcrypto-1.0.0.dll .) *Compared to 4.0.1.3, bug #229 (support for https broker connections) was fixed. However, it was also fixed in 4.0.1.3+build2. This bugfix is being mentioned here because some users may not be aware of 4.0.1.3+build2. (Ironically, the fix was to add ssleay32.dll, which means that the heartbleed vulnerability was only ever present in 4.0.1.3+build2.) *The following security vulnerabilities in VcXsrv: CVE-2013-4396 (Oct. 8, 2013), CVE-2013-6462 (Jan. 7, 2014) (Note that we have not determined whether or not X2Go could actually trigger them. They are however now fixed in the VcXsrv code.) ===== Noteworthy Windows-Specific Bugs ===== * [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=108|bug 108]] - Certain specialized applications fail to start (or exhibit font-related bugs) due to the fonts not being installed on the X2Go Client. This can be worked around by using the x2goclient-4.0.2.0-miscfonts-setup.exe installer located here: http://code.x2go.org/releases/binary-win32/x2goclient/tmp/ . If the problem still persists, try using x2goclient-4.0.2.0-fullfonts-setup.exe instead. Note that these installers are a temporary measure until a permanent solution is implemented. * [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=109|bug 109]] - x2goclient refuses to start after selecting a nonexistent external X server. To prevent this bug, do not select to use an external X server without specifying the path to an external X server that is actually installed. (The default path usually does not exist.) If you are experiencing this bug, work around it by setting this registry value: HKEY_CURRENT_USER\Software\Obviously Nice\x2goclient\settings\useintx = true -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:start
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:54 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:start?rev=1377601964 New Revision: http://wiki.x2go.org/doku.php/doc:start Edit Summary: Add Windows-Specific Release Notes User : mikedep333 @@ -4,8 +4,9 @@ * [[doc:newtox2go|New to X2Go? Start here!]] * [[doc:installation:start|Installing X2Go]] * [[doc:usage:start|Using X2Go]] + * [[doc:release-notes-mswin|Windows-Specific Release Notes]] * [[wiki:development:join-the-team|Participate in X2Go]] * [[doc:organigram|Who is who in X2Go]] * [[doc:professional-support|Professional Support]] * [[doc:sponsors|Development Sponsoring]] @@ -24,6 +25,5 @@ ===== Translating the X2Go Wiki ===== * Translating the main wiki pages to other languages than English (in prep) FIXME - -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page added: doc:release-notes-mswin
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

1 0

page changed: doc:release-notes-mswin:x2goclient-4.0.2.0
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:50 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0?re… New Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0 Edit Summary: Clarify builds User : mikedep333 @@ -29,12 +29,23 @@ *http://code.x2go.org/releases/binary-win32/3rd-party/pulse/ ===== Available Builds ===== The regular build is available here: - *http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.0/x2goclient-4.0.2.0-setup.exe - Until a new version of X2Go Client is released, this link on the home page is the aforementioned version & build: - *http://code.x2go.org/releases/X2GoClient_latest_mswin32-setup.exe - There is no longer an "interims" build with PulseAudio 0.9.6 because PulseAudio 1.1 has been upgraded to PulseAudio 5.0, and it includes a fix for X2Go Bug 363. If a regression is discovered in PulseAudio 5.0, an "interims" build with PulseAudio 0.9.6 will be released. + * http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.0/x2go… + + <note>Until a new version of X2Go Client is released, this link on the home page is the aforementioned version & build: + http://code.x2go.org/releases/X2GoClient_latest_mswin32-setup.exe</note> + + <note tip>There is no longer an "interims" build with PulseAudio 0.9.6 because PulseAudio 1.1 has been upgraded to PulseAudio 5.0, and it includes a fix for X2Go Bug 363. If a regression is discovered in PulseAudio 5.0, an "interims" build with PulseAudio 0.9.6 will be released.</note> + + The "misc" fonts build is available here. See the "Noteworthy Windows-Specific Bugs" below for more info. + * http://code.x2go.org/releases/binary-win32/x2goclient/tmp/x2goclient-4.0.2.… + + The "full" fonts build is available here. See the "Noteworthy Windows-Specific Bugs" below for more info. + * http://code.x2go.org/releases/binary-win32/x2goclient/tmp/x2goclient-4.0.2.… + + A debug build is available here. If you experience a bug and would like to assist with debugging it, this build is for you. It does not include any of the fonts. + * http://code.x2go.org/releases/binary-win32/x2goclient/tmp/x2goclient-4.0.2.… ===== Compatible Windows Versions ===== 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. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:release-notes-mswin:x2goclient-4.0.2.0
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:36 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0?re… New Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0 Edit Summary: User : mikedep333 @@ -1,6 +1,5 @@ ====== Windows-Specific Release notes for X2Go Client 4.0.2.0 ====== - ====== THIS IS STILL A DRAFT ====== ===== Major Windows-specific changes since 4.0.1.3+build2 ===== === Continued compatibility with Windows XP === Since version 3.99.0.0, X2Go Client for Windows has bundled VcXsrv. VcXsrv is the only port of the X.org X Server to Windows that is both actively maintained and open source. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:release-notes-mswin:x2goclient-4.0.2.0
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:33 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0?re… New Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0 Edit Summary: [Noteworthy Windows-Specific Bugs] User : mikedep333 @@ -74,5 +74,6 @@ *The following security vulnerabilities in VcXsrv: CVE-2013-4396 (Oct. 8, 2013), CVE-2013-6462 (Jan. 7, 2014) (Note that we have not determined whether or not X2Go could actually trigger them. They are however now fixed in the VcXsrv code.) ===== Noteworthy Windows-Specific Bugs ===== - * [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=108|bug 108]] - certain specialized applications fail to start (or exhibit font-related bugs) due to the fonts not being installed on the X2Go Client. This can be worked around by using the x2goclient-4.0.2.0-miscfonts-setup.exe installer located here: http://code.x2go.org/releases/binary-win32/x2goclient/tmp/ . If the problem still persists, try using x2goclient-4.0.2.0-fullfonts-setup.exe instead. Note that these installers are a temporary measure until a permanent solution is implemented. + * [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=108|bug 108]] - Certain specialized applications fail to start (or exhibit font-related bugs) due to the fonts not being installed on the X2Go Client. This can be worked around by using the x2goclient-4.0.2.0-miscfonts-setup.exe installer located here: http://code.x2go.org/releases/binary-win32/x2goclient/tmp/ . If the problem still persists, try using x2goclient-4.0.2.0-fullfonts-setup.exe instead. Note that these installers are a temporary measure until a permanent solution is implemented. + * [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=109|bug 109]] - x2goclient refuses to start after selecting a nonexistent external X server. To prevent this bug, do not select to use an external X server without specifying the path to an external X server that is actually installed. (The default path usually does not exist.) If you are experiencing this bug, work around it by setting this registry value: HKEY_CURRENT_USER\Software\Obviously Nice\x2goclient\settings\useintx = true -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:release-notes-mswin:x2goclient-4.0.2.0
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:26 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0?re… New Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0 Edit Summary: add bug 108 (missing fonts) User : mikedep333 @@ -71,4 +71,8 @@ The following bugfixes are not mentioned in the regular release notes. (They are not mentioned in the regular release notes because they do not consist of fixes to X2GoClient's source code, only to the dependencies bundled.): *CVE-2014-0160 "Heartbleed" vulnerability (Note: X2Go Client was only affected by the heartbleed vulnerability when connecting to a an X2Go session broker over HTTPS. Even though X2Go Client uses libssh and cygwin's openssh, which both in turn use openssl, they were never affected because the SSH protocol does not contain the SSL heartbeat. For more info on why SSH implementations are not affected, read [[https://access.redhat.com/site/solutions/786603|Red hat's solution article.]]. The only difference between that solution article and X2Go Client is that the vulnerable library file is ssleay32.dll and the non-affected library files are both libeay32.dll and cygcrypto-1.0.0.dll .) *Compared to 4.0.1.3, bug #229 (support for https broker connections) was fixed. However, it was also fixed in 4.0.1.3+build2. This bugfix is being mentioned here because some users may not be aware of 4.0.1.3+build2. (Ironically, the fix was to add ssleay32.dll, which means that the heartbleed vulnerability was only ever present in 4.0.1.3+build2.) *The following security vulnerabilities in VcXsrv: CVE-2013-4396 (Oct. 8, 2013), CVE-2013-6462 (Jan. 7, 2014) (Note that we have not determined whether or not X2Go could actually trigger them. They are however now fixed in the VcXsrv code.) + + ===== Noteworthy Windows-Specific Bugs ===== + + * [[http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=108|bug 108]] - certain specialized applications fail to start (or exhibit font-related bugs) due to the fonts not being installed on the X2Go Client. This can be worked around by using the x2goclient-4.0.2.0-miscfonts-setup.exe installer located here: http://code.x2go.org/releases/binary-win32/x2goclient/tmp/ . If the problem still persists, try using x2goclient-4.0.2.0-fullfonts-setup.exe instead. Note that these installers are a temporary measure until a permanent solution is implemented. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:release-notes-mswin:x2goclient-4.0.2.0
by wiki-admin＠x2go.org 24 Apr '14

24 Apr '14

A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/24 00:18 Browser : Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 IP-Address : 72.94.83.13 Hostname : pool-72-94-83-13.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0?re… New Revision: http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0 Edit Summary: [Windows-Specific Bug Fixes] Add info on bug#229 fix. User : mikedep333 @@ -64,10 +64,11 @@ ===== Windows-Specific Bug Fixes ===== As mentioned in the regular release notes: *Reapply KDE on Windows's patch for Pageant support to libssh 0.5.5. (Fixes: #448) + *Fix compatibility with PulseAudio 3.0 & later through new cookie handling. (Fixes: #422) *The regular build X2Go Client now includes a fix for bug #363 (choppy audio in Flash Player). Users no longer need to install an "interims" build for that a fix. The following bugfixes are not mentioned in the regular release notes. (They are not mentioned in the regular release notes because they do not consist of fixes to X2GoClient's source code, only to the dependencies bundled.): *CVE-2014-0160 "Heartbleed" vulnerability (Note: X2Go Client was only affected by the heartbleed vulnerability when connecting to a an X2Go session broker over HTTPS. Even though X2Go Client uses libssh and cygwin's openssh, which both in turn use openssl, they were never affected because the SSH protocol does not contain the SSL heartbeat. For more info on why SSH implementations are not affected, read [[https://access.redhat.com/site/solutions/786603|Red hat's solution article.]]. The only difference between that solution article and X2Go Client is that the vulnerable library file is ssleay32.dll and the non-affected library files are both libeay32.dll and cygcrypto-1.0.0.dll .) + *Compared to 4.0.1.3, bug #229 (support for https broker connections) was fixed. However, it was also fixed in 4.0.1.3+build2. This bugfix is being mentioned here because some users may not be aware of 4.0.1.3+build2. (Ironically, the fix was to add ssleay32.dll, which means that the heartbleed vulnerability was only ever present in 4.0.1.3+build2.) *The following security vulnerabilities in VcXsrv: CVE-2013-4396 (Oct. 8, 2013), CVE-2013-6462 (Jan. 7, 2014) (Note that we have not determined whether or not X2Go could actually trigger them. They are however now fixed in the VcXsrv code.) - * -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

x2go-commits April 2014