x2go-dev

x2go-dev@lists.x2go.org

2 participants
5403 discussions

Bug#333: Users can inject arbitrary data into X2Go Client via .bashrc
by Mike Gabriel 29 Oct '13

29 Oct '13

Hi All, Dan Halbert made me aware of it being easily possible to inject arbitrary data into X2Go Client via the server-side .bashrc file. This surely is a security problem in X2Go. Thus, I found that we really need to do some sanity checks on incoming output from X2Go Servers to avoid such injections. The idea is to invoke the server-side command with a UUID hash before and after the actuall command invocation: 1. execute server-side command from X2Go Client: ssh <user>@<server> sh -c "echo <uuidhash> && <x2gocmd> && echo <uuidhash> 2. read data from X2Go Server: X2GODATABEGIN:<uuidhash> <x2godata_line1> <x2godata_line2> .... <x2godata_lineN> X2GODATAEND:<uuidhash> 3. cut out the X2Go data returned by the server (in C++): QString begin_marker = "X2GODATABEGIN:"+uuid+"\n"; QString end_marker = "X2GODATAEND:"+uuid+"\n"; int output_begin=stdOutString.indexOf(begin_marker) + \\ begin_marker.length(); int output_end=stdOutString.indexOf(end_marker); output = stdOutString.mid(output_begin, \\ output_end-output_begin); I have a patch locally for this and will commit it in a minute. We can discuss the patch and move on from there when it's there. Unfortunately, this patch does not fix #327 as it is impossible to use scp with echoing .bashrc files. With this patch applied, the session starts, but setting up the SSHfs shares fails with locking up X2Go Client. For people who depend on echoing .bashrc files, please read my last post on #327. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 2

Bug#333: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike Gabriel 29 Oct '13

29 Oct '13

tag #333 pending fixed #333 4.0.1.2 thanks Hello, X2Go issue #333 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=c121b7e The issue will most likely be fixed in src:x2goclient (4.0.1.2). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit c121b7e2d3d83abdc2d7a29637bc3294e38b2ec3 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Tue Oct 29 13:36:58 2013 +0100 Perform sanity checks on data that comes in from X2Go Servers. Prohibit the execution of arbitrary code via the ~/.bashrc file. (Fixes: #333). diff --git a/debian/changelog b/debian/changelog index e484ba5..e069591 100644 --- a/debian/changelog +++ b/debian/changelog @@ -8,6 +8,9 @@ x2goclient (4.0.1.2-0~x2go2) UNRELEASED; urgency=low + Store broker HTTPS certificate exceptions in $HOME/.x2go/ssl/exceptions (before: $HOME/ssl/exceptions). (Fixes: #328). + + Perform sanity checks on data that comes in from X2Go Servers. + Prohibit the execution of arbitrary code via the ~/.bashrc file. + (Fixes: #333). * Pull-in packaging changes from Debian. [ Ricardo Díaz Martín ]

3 3

Bug#327: x2go client crashes if .bashrc prints anything
by Dan Halbert 29 Oct '13

29 Oct '13

Package: x2goclient Version: 4.0.0.3 If I put an echo "testing" # exact text doesn't matter at the top of my .bashrc, then the x2goclient crashes immediately when trying to start a session. (The crash does not occur if I put a similar statement in .bash_login.) I have reproduced this on the Windows client; I believe a colleague saw it on both the Windows and Linux clients. The x2go server being used is 4.0.1.6-0~712~precise1.

3 5

Bug#321: X2Go issue (in src:pyhoca-gui) has been marked as pending for release
by Mike Gabriel 29 Oct '13

29 Oct '13

tag #321 pending fixed #321 0.4.0.9 thanks Hello, X2Go issue #321 (src:pyhoca-gui) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=299bb0e The issue will most likely be fixed in src:pyhoca-gui (0.4.0.9). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 299bb0ee83d70c6c98cbc834e7d876cdff27d91f Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Tue Oct 29 09:58:24 2013 +0100 Don't crash if no notification-daemon provide is registered in DBUS. (Fixes: #321). diff --git a/debian/changelog b/debian/changelog index 131085e..9abb3f9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -8,6 +8,8 @@ pyhoca-gui (0.4.0.9-0~x2go1) UNRELEASED; urgency=low - Support encrypted on SSH proxy whith password authentication on X2Go Server. - Implement two-factor authentication. + - Don't crash if no notification-daemon provide is registered in DBUS. + (Fixes: #321). * /debian/copyright: + Update file. Add entry for file icon2exe.py.

2 1

x2go session broker connect problem
by Ted Barnes 29 Oct '13

29 Oct '13

Hi All: Am trying to get up to speed on x2go session broker, but am having trouble. Any suggestions? When try to connect I get: Error Login failed! Please try again. Along with... broker url: http://xxx.xxx.xxx.xxx/:8080/plain/inifilebroker url:http://xxx.xxxx.xxx.xxx/:8080/plain/inifile or.... broker url:http://user@xxx.xxx.xxx.xxx/cgi-bin/x2gobroker.cfgi As I'm getting started, I'm trying to do this on my LAN (all behind my firewall) without any ssh (longer term I want to see if I can run sessions inside SSL). I've disabled all the iptable rules on my server....and tried various settings in the x2gobroker.conf and x2gobroker-sessionprofiles.conf files which have not really changed the error message but may be the problem (see below). I can connect using the x2go client GUI "the normal way", and the first time I got a window on the client "The server is unknown. Do you trust the host key....", which I assume is x2go dynamically creating a ssh tunnel? This part works fine. However, when I try from the command line with an "x2goclient --broker-..." type of command, I get the Error message. Both client and server are running Debian Squeeze, and on the server I've successively installed: x2gobroker-wsgi apache2 libapache20mod-wsgi x2gobroker-authservice (wasn't sure if I should install this for my initial tests) My x2gobroker.conf: # This file is part of the X2Go Project - http://www.x2go.org # Copyright (C) 2011-2013 by Oleksandr Shneyder <oleksandr.shneyder(a)obviously-nice.de> # Copyright (C) 2011-2013 by Heinz-Markus Graesing <heinz-m.graesing(a)obviously-nice.de> # Copyright (C) 2012-2013 by Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> # # X2Go Session Broker is free software; you can redistribute it and/or modify # it under the terms of the GNU Affero General Public License as published by # the Free Software Foundation; either version 3 of the License, or # (at your option) any later version. # # X2Go Session Broker is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU Affero General Public License for more details. # # You should have received a copy of the GNU Affero General Public License # along with this program; if not, write to the # Free Software Foundation, Inc., # 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. ### ### GLOBAL section ### [global] # Allow unauthenticated connections? Then set check-credentials to false. check-credentials = false # To secure server-client communication the client can start the communication # with a pre-set, agreed on authentication ID. Set the below value to true # to make the X2Go Session Broker require this feature #require-cookie-auth = false ### NOT-IN-USE-YET # X2Go supports two different cookie authentication modes (static and dynamic). #use-static-cookie = false ### NOT-IN-USE-YET # Every server-client communication (between X2Go Client and broker) has to be # accompanied by this initial authentication cookie. #my-cookie = <aaaavveeeerrrrryyyyylooonnnnggggssttrrriiinnnggg> ### NOT-IN-USE-YET # X2Go Session Broker knows about two output formats: a text/plain based output # and a text/json based output that is compatible with UCCS. The different outputs # run under different URLs. enable {base_url}/plain/ enable-plain-output = true # enable {base_url}/uccs/ #enable-uccs-output = false # use this URL base to create URL field in UCCS-style JSON output #my-uccs-url-base = http://localhost:8080/ # default authentication mechanism for all broker backends default-auth-mech = pam # how does this X2Go Session Broker instance retrieve user and group # information from the system? (defaults for all broker backends) default-user-db = libnss default-group-db = libnss # on large deployments it is recommended to ignore primary group # memberships traversing into all user accounts for primary group # detection can be quite CPU intensive on the X2Go Broker server. #ignore-primary-group-memberships = true # X2Go session autologin via X2Go Session Broker # # Once authenticated against the session # broker, the user becomes a trusted user. That is, the X2Go session login can # be automatized by a very temporary SSH pub/priv key pair. Prior to the session # login the key is generated, after successful session login, the key is dropped # immediately. # # This option can be overridden by the session profile parameter # broker-session-autologin={true|false} broker-session-autologin=true default-session-autologin=true # X2Go's authorized_keys file for broker mediated autologin sessions # # For the X2Go auto-login via X2Go Session Broker feature to work thoroughly, # the X2Go Session Broker has to place the temporary public SSH key into the # user's home directory. It is not recommended to use SSH's default # authorized_keys file for this but a separate and X2Go-specific authorized_keys # file ($HOME/.x2go/authorized_keys). # # Of course, the SSH daemon has to be made aware of this. This can be configured # in /etc/ssh/sshd_config like this: # # --- /etc/ssh/sshd_config.no-x2go 2013-03-01 09:57:04.000000000 +0100 # +++ /etc/ssh/sshd_config 2013-03-01 09:56:57.000000000 +0100 # @@ -28,7 +28,8 @@ # # RSAAuthentication yes # PubkeyAuthentication yes # AuthorizedKeysFile %h/.ssh/authorized_keys # +AuthorizedKeysFile2 %h/.x2go/authorized_keys # # # Don't read the user's ~/.rhosts and ~/.shosts files # IgnoreRhosts yes # # This option can be overridden by the session profile parameter # broker-authorized-keys=<file-location> #default-authorized-keys=%h/.x2go/authorized_keys # X2Go Broker Agent query mode # # The X2Go Broker Agent is needed for multi-server sites configured for # load balancing. Multi-server sites require a setup that uses the # PostgreSQL X2Go session DB backend. The X2Go Broker Agent has to be installed # on the local system (mode: LOCAL) or on all X2Go Servers (mode: SSH) in a # multi-server farm. # # So, there are three query modes for the X2GO Broker Agent: NONE, LOCAL and # SSH. # # NONE - Try to get along without X2Go Broker Agent queries. For simple # broker setups this may suffice. For load-balancing or reliable # session suspending and resuming the broker agent is a must!!! # # LOCAL - This LOCAL mode only works for _one_ configured multi-server farm. # If this X2Go Session Broker is supposed to serve many different # multi-server farms, then the LOCAL mode will not work!!! # # How it works: Assume that the local system has an X2Go Broker Agent # that knows about the multi-server setup. This means: X2Go Server # has to be installed locally and the X2Go Server has to be # configured to use the multi-server farm's PostgreSQL session DB # backend. # # The local system that is running the broker does not necessarily # have to be a real application server. It only has to be aware of # running/suspended sessions within the X2Go multi-server farm setup. # # A typical use-case is X2Go on top of a Debian Edu Terminal-Server # farm: # # TJENER -> PostgreSQL DB, X2Go Server, X2Go Session Broker + # Broker Agent # TS01 - TS0X -> X2Go Server configured to use the PostgreSQL DB # on TJENER # # SSH - The more generic approach, but also more complex. It allows that # the broker on this system may serve for many different X2Go Server # multi-server setups. # # With the SSH agent query mode, the X2Go Session Broker will query # one of the X2Go Servers in the targeted multi-server setup (through # SSH). The SSH authentication is done by a system user account # (normally UID=x2gobroker) and SSH pub/priv key authentication has # to be configured to make this work. # # All X2Go Servers in a multi-server farm need the X2Go Broker Agent # installed, whereas this local system running the X2Go Session # Broker does not need a local X2Go Broker Agent at all. # # The agent query mode can be configured on a per-broker-backend basis, the # below value is the default. #default-agent-query-mode=LOCAL ### ### BACKEND section ### # Possible X2Go Session Broker backends: # # 1. backend = zeroconf (activated by default) # Use the ZeroConf X2Go Session Broker backend, this backend is for demo only # and only operates on localhost. Make sure you have x2gobroker-daemon and # and x2goserver installed on the same machine. No need to install # x2gobroker-agent. # 2. backend = infile (deactivated by default) # The IniFile X2Go Session Broker backend is for providing session profiles # to multiple users/clients on a text config file basis (.ini file format). # # The session profile setup is accomplished by an extra configuration file, # by default named /etc/x2go/broker/x2gobroker-sessionproiles.conf. # # For small-scale deployments the IniFile backend is the recommended backend. [zeroconf] #enable = true #auth-mech = pam #user-db = libnss #group-db = libnss #desktop-shell = KDE [inifile] enable = true session-profiles = /etc/x2go/broker/x2gobroker-sessionprofiles.conf #[ldap] -> MUSIC OF THE FUTURE #enable = false #auth-mech = ldap #user-db = ldap #group-db = ldap #uri = ldap://localhost:389 #base = dc=example,dc=org #user-search-filter = (&(objectClass=posixAccount)(uid=*)) #host-search-filter = (&(objectClass=ipHost)(serial=X2GoServer)(cn=*)) #group-search-filter = (&(objectClass=posifxGroup)(cn=*)) #starttls = false #agent-query-mode = SSH My x2gobroker-sessionprofiles.conf: ### X2Go Broker Session Profiles - ADAPT TO YOUR NEEDS ### # This whole file reflects a set of examplary X2Go session profiles being # provided via the X2Go Session Broker (backend: iniconf). # This whole file could be the broker setup in some university institute that # runs three server pools (pool-A, pool-B and pool-C). Though most univerities # have real IPv4 internet addresses, we use private subnets in the examples # below. # The X2Go Session Broker is served into the institutes local intranet, the # broker cannot be reached from the internet directly. # The first section [DEFAULTS] provides a set of default profile settings that # are common to all session profiles given in sections below. # The other section names can be freely chosen, however, each section name has # to be unique within this file. # IMPORTANT: in the session profiles below you will find some lines starting # with acl-... These lines do neither protect the X2Go Session Broker nor # your X2Go Servers. They simply allow for selective session profile provision # based on client address, user name and group memberships. # # For protecting the broker use iptables and ip6tables. For protecting your # X2Go Servers use iptable+ip6tables and a tightened PAM configuration (e.g. # pam_access.so). Securing X2Go Servers means securing the SSH daemon that # runs on the X2Go Server. [DEFAULT] command=TERMINAL defsndport=true useiconv=false iconvfrom=UTF-8 height=600 export= quality=9 fullscreen=false layout= useexports=true width=800 speed=2 soundsystem=pulse print=true type=auto sndport=4713 xinerama=true variant= usekbd=true fstunnel=true applications=TERMINAL,WWWBROWSER,MAILCLIENT,OFFICE multidisp=false sshproxyport=22 sound=true rootless=false iconvto=UTF-8 soundtunnel=true dpi=96 sshport=22 setdpi=0 pack=16m-jpeg directrdp=false [GNOME] user=xxx host=xxx.xxx.xxx.xxx name=GNOME command=GNOME rootless=false acl-users-allow=xxx acl-groups-allow=gnome-users,admins acl-groups-deny=ALL acl-any-order=deny-allow broker-session-autologin=true

2 1

Re: [X2Go-Dev] X2Go-Dev Digest, Vol 58, Issue 16
by Madog 24 Oct '13

24 Oct '13

Thanks Mike (!) - that did the trick... On Oct 24, 2013, at 6:00 AM, x2go-dev-request(a)lists.berlios.de wrote: > Send X2Go-Dev mailing list submissions to > x2go-dev(a)lists.berlios.de > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.berlios.de/mailman/listinfo/x2go-dev > or, via email, send a message with subject or body 'help' to > x2go-dev-request(a)lists.berlios.de > > You can reach the person managing the list at > x2go-dev-owner(a)lists.berlios.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of X2Go-Dev digest..." > > > Today's Topics: > > 1. Bug#331: Default umask when mounting sshfs tunnel (Helmer Teles) > 2. x2go session broker & apache (Ted Barnes) > 3. Re: x2go session broker & apache (Mike Gabriel) > 4. X2Goclient portable (Tobias Luther | X2Go-Community.org) > 5. Re: X2Goclient portable (Stefan Baur) > 6. Processed: X2Go issue (in src:x2goserver) has been marked as > pending for release (X2Go Bug Tracking System) > 7. Bug#331: X2Go issue (in src:x2goserver) has been marked as > pending for release (Mike Gabriel) > 8. Re: client inconsistencies when resizing GNOME sessions > (Mike Gabriel) > 9. Bug#330: X2Go issue (in src:python-x2go) has been marked as > pending for release (Mike Gabriel) > 10. Bug#329: X2Go issue (in src:python-x2go) has been marked as > pending for release (Mike Gabriel) > 11. Processed: X2Go issue (in src:python-x2go) has been marked as > pending for release (X2Go Bug Tracking System) > 12. Processed: X2Go issue (in src:python-x2go) has been marked as > pending for release (X2Go Bug Tracking System) > 13. Bug#328: X2Go issue (in src:x2goclient) has been marked as > pending for release (Mike Gabriel) > 14. Processed: X2Go issue (in src:x2goclient) has been marked as > pending for release (X2Go Bug Tracking System) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 23 Oct 2013 13:44:47 +0100 > From: Helmer Teles <helmer.teles(a)mykolab.com> > To: submit(a)bugs.x2go.org > Subject: [X2Go-Dev] Bug#331: Default umask when mounting sshfs tunnel > Message-ID: <1456688.sWGnl1COIA@zen-touch> > Content-Type: text/plain; charset="iso-8859-1" > > Package: x2goserver > Version: 4.0.1.6-0~712~precise1 > Tag: Patch > > Hello dear mates. > > > Just had a problem that when a user moves or copy a file from the mounted sshfs dir to > a shared directory on the x2goserver, if this is a shared folder for a group with > respective ACL's we've got a problem with the final permissions. > > > The easy way to solve this is to change the x2gomountdirs to include the umask param. > > > Also included is the modification required at /etc/x2goserver.conf > If stay uncommented the umask will stay as is on the server side ( client local computer > ) and the value provided ( 0117 ) will make all files to be with rw-rw---- > > > P.S: As i don't have the original x2goserver.conf don't apply the diff as is, but use it as > reference please. > > > the diff's are attached as Mr. Michael kindly asked. > > > Best regards, > > > -- > Com os melhores cumprimentos. > Helmer Teles > > http://hteles.wordpress.com[1] > > "Sent from my Linux Device" > Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC > 26300) > > > > -------- > [1] http://hteles.wordpress.com/ >

1 0

Bug#328: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike Gabriel 24 Oct '13

24 Oct '13

tag #328 pending fixed #328 4.0.1.2 thanks Hello, X2Go issue #328 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=cf33d55 The issue will most likely be fixed in src:x2goclient (4.0.1.2). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit cf33d551c21c86c7ea654914930550b0fd0b2c79 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Thu Oct 24 10:10:53 2013 +0200 Store broker HTTPS certificate exceptions in $HOME/.x2go/ssl/exceptions (before: $HOME/ssl/exceptions). (Fixes: #328). diff --git a/debian/changelog b/debian/changelog index 05b5189..e484ba5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -5,6 +5,9 @@ x2goclient (4.0.1.2-0~x2go2) UNRELEASED; urgency=low + Provide Keywords: key in .desktop file. + Add NSIS packaging files for win32 builds to source tree. (Files provided by Oleksandr Shneyder, thanks!!!). + + Store broker HTTPS certificate exceptions in + $HOME/.x2go/ssl/exceptions (before: $HOME/ssl/exceptions). + (Fixes: #328). * Pull-in packaging changes from Debian. [ Ricardo Díaz Martín ]

2 1

Bug#329: X2Go issue (in src:python-x2go) has been marked as pending for release
by Mike Gabriel 24 Oct '13

24 Oct '13

tag #329 pending fixed #329 0.4.0.9 thanks Hello, X2Go issue #329 (src:python-x2go) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=6bc5020 The issue will most likely be fixed in src:python-x2go (0.4.0.9). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 6bc50204f851133b284e8f3ba388101118fae2f9 Author: Orion Poplawski <orion(a)cora.nwra.com> Date: Thu Oct 24 09:54:59 2013 +0200 debian/control: Drop python-cups from Depends: field. Python CUPS is no dependency if Python X2Go. (Fixes: #329). diff --git a/debian/changelog b/debian/changelog index de471fb..ac9dc1e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -17,6 +17,11 @@ python-x2go (0.4.0.9-0~x2go1) UNRELEASED; urgency=low - Rewrite passwords that are not string/unicode to an empty string. - No Unicode chars in log messages. Eliminated one more in checkhosts.py. + [ Orion Poplawski ] + * debian/control: + + Drop python-cups from Depends: field. Python CUPS is no dependency if + Python X2Go. (Fixes: #329). + [ Kenneth Pedersen ] * New upstream version (0.4.0.9): - Color depth detection: Stop using win32api.GetSystemMetrics(2) which actually

2 1

Bug#330: X2Go issue (in src:python-x2go) has been marked as pending for release
by Mike Gabriel 24 Oct '13

24 Oct '13

tag #330 pending fixed #330 0.4.0.9 thanks Hello, X2Go issue #330 (src:python-x2go) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=732635e The issue will most likely be fixed in src:python-x2go (0.4.0.9). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 732635efb177910d23b544d2e05e09559c8af5ff Author: Kenneth Pedersen <kenneth(a)wangpedersen.com> Date: Thu Oct 24 09:50:00 2013 +0200 Color depth detection: Stop using win32api.GetSystemMetrics(2) which actually returns the width of a vertical scroll bar in pixels. Instead, create a screen display context and query it for the color depth. (Fixes: #330). diff --git a/debian/changelog b/debian/changelog index 8c6ee9e..de471fb 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,6 @@ python-x2go (0.4.0.9-0~x2go1) UNRELEASED; urgency=low + [ Mike Gabriel ] * New upstream version (0.4.0.9): - Agent channels in Paramiko can raise an EOFError if the connection has got disrupted. Ignoring this. @@ -16,6 +17,12 @@ python-x2go (0.4.0.9-0~x2go1) UNRELEASED; urgency=low - Rewrite passwords that are not string/unicode to an empty string. - No Unicode chars in log messages. Eliminated one more in checkhosts.py. + [ Kenneth Pedersen ] + * New upstream version (0.4.0.9): + - Color depth detection: Stop using win32api.GetSystemMetrics(2) which actually + returns the width of a vertical scroll bar in pixels. Instead, create a screen + display context and query it for the color depth. (Fixes: #330). + -- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Wed, 07 Aug 2013 12:18:46 +0200 python-x2go (0.4.0.8-0~x2go1) unstable; urgency=low

2 1

client inconsistencies when resizing GNOME sessions
by Pedro Pinto 24 Oct '13

24 Oct '13

Hi Guys, I've found some inconsistent X2GO client behaviour, and was hoping someone could shed some light. In short, it seems that the C++ x2goclient for Mac is able to handle "session resizing" correctly, but Pyhoca-GUI for Linux isn't, even though they are configured with exaclty the same session parameters. Specifically: --- when I start a GNOME-fallback session using the Pyhoca-GUI for Linux, the remote desktop appears with a "constant geometry", where resizing the local session window simply crops the view of the remote GNOME-fallback desktop. -- on the other hand, using the C++ x2go client for Mac, I can successfuly resize the local session window, and the remote GNOME-fallback desktop also resizes automatically. -- strangely, I can get Pyhoca-GUI to *also* resize properly if I do the following: 1) Start a GNOME-fallback session with the C++ x2goclient for Mac, then suspend the session. 2) Use Pyhoca-GUI for linux to resume the session in 1). Then, Pyhoca-GUI is able to handle session resizing properly, ie, resizing the local session window will resize the remote GNOME desktop. This last point suggests that the resizing issue is not a GNOME bug, but an issue with the X2GO client. Also, let me mention how this relates to the bug in http://bugs.x2go.org/42. Using the C++ x2goclient for Mac, I verified that this happens: o with GNOME3 the window appears in the expected size and then gets resized from inside the starting up GNOME3 session but these don't: o I can manually resize the window afterwards via the client-side window manager (play with your mouse on the window borders...) o Still, the desktop shell inside does not adapt its size On the contrary, the C++ X2goclient is able to perform the auto-resizing correctly. Versions that I'm using: -- C++ X2goclient for Mac, version 4.0.1.0 -- Pyhoca GUI for Linux, version 0.4.0.8 -- x2goagent: 3.5.0.20 -- x2goserver: 4.0.1.6 -- x2goserver-extensions: 4.0.1.6 -- x2goserver-pyhoca: 4.0.1.6 -- x2goserver-xsession: 4.0.1.6 A last, related question that perhaps someone can point me in the right direction: I'd like to implement a "stretch/compress" resizing behaviour, where: --- the resolution of the remote GNOME-fallback session is always constant (say 1280x720). --- when the user resizes the local session window, it does *not* modify the resolution of the remote GNOME-fallback session, but simply distorts it (stretch/compress) so that it fits the window exactly. Is this possible at all? If so, where should I start looking to implement this feature? Many thanks, Pedro

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev