x2go-dev August 2018

x2go-dev@lists.x2go.org

14 participants
105 discussions

Bug#1296: x2gobroker-ssh : wrong password after password change in interactive mode
by Walid MOGHRABI 12 Sep '18

12 Sep '18

package: x2gobroker-ssh version: 0.0.4.0-0~1022~ubuntu16.04.1 priority: bug x2gobroker-ssh supports interactive mode which means that it can reports login interactions to the user such as password changes requests. Let's say that my user's password has expired, when I login to the broker with x2goclient in broker mode, I'll see a new form asking for my old password and I must type/confirm my new password. Once done, I'll be granted access to the broker and I'll get my session profiles list on the right sidebar of the client. Since I'm using --use-broker-pass, I don't have to re-type my password when connecting to a session but in that specific use case, I get an auth error while connecting because of wrong password. In fact, it appears that the client keeps the first password that has been entered at the broker login prompt (the one that expired) when passing it to the session profile. Once you get the auth error, you'll be prompted with user/pass for the session profile, if you enter the new password, then it works. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

3 5

Bug#1012: Session reconnect doesn't work (x2gobroker)
by Stefan Baur 07 Sep '18

07 Sep '18

package: x2gobroker version: 0.0.3.0 Situation: two identical nodes, only difference is DNS name + IP Desired result: load-balanced X2Go systems, where a suspended session can be resumed Actual outcome: Each connect starts a new session, suspended sessions are left dangling forever Questions: 1) Is x2gobroker-daemon needed at all for ssh-only connections to the broker? 2) Did I miss any obvious steps? 3) What would be the suggested path to debug this? A full typescript recording of the installation process is available, but as no command returned any error messages, let me shorten it down to the commands that were executed: # commands executed on both first and second node apt-get install x2gobroker -y cp /etc/x2go/x2gobroker.conf /etc/x2go/x2gobroker.conf.orig vi /etc/x2go/x2gobroker.conf # see diff below apt-get install x2gobroker-agent -y cp /etc/x2go/broker/x2gobroker-sessionprofiles.conf /etc/x2go/broker/x2gobroker-sessionprofiles.conf.orig vi /etc/x2go/broker/x2gobroker-sessionprofiles.conf # see diff below x2gobroker-keygen cp /var/lib/x2gobroker/.ssh/id_rsa.pub /tmp/ cd /tmp/ vi id_rsa.pub # added a blank and the server name to end of file python -m SimpleHTTPServer 8081 # run temporary web server so second node can fetch the file # once both web servers were up, the following commands were executed # on BOTH nodes: x2gobroker-pubkeyauthorizer -t http://firstnode:8081/id_rsa.pub x2gobroker-pubkeyauthorizer -t http://secondnode:8081/id_rsa.pub # Sadly, no working session reconnect with these command line # parameters - it always starts a new session: x2goclient --broker-url=ssh://accountwithapublickey@firstnode:22/usr/bin/x2gobroker --broker-autologin # This is using x2goclient-4.0.5.0-2015.07.31 # taking a closer look at # http://wiki.x2go.org/doku.php/doc:installation:x2gobroker: # maybe x2gobroker-daemon is missing? So ... apt-get install x2gobroker-daemon -y # this also pulls in x2gobroker-authservice # Sadly, no change, still no working session reconnect :-( # --------------------------------------------------------- diff -u /etc/x2go/x2gobroker.conf.orig /etc/x2go/x2gobroker.conf --- /etc/x2go/x2gobroker.conf.orig 2016-03-19 18:39:02.034407506 +0100 +++ /etc/x2go/x2gobroker.conf 2016-03-19 19:56:05.781729565 +0100 @@ -241,6 +241,7 @@ # The agent query mode can be configured on a per-broker-backend basis, the # below value is the default. #default-agent-query-mode=NONE +default-agent-query-mode=SSH # Probe SSH port of X2Go Servers (availability check) # @@ -254,7 +255,7 @@ # Per default, we set this to "true" here. The portscan feature can be # deactivated on a per-session-profile basis (use: broker-portscan-x2goservers = # false in the session profile configuration). -#default-portscan-x2goservers = true +default-portscan-x2goservers = false # Use load checker for querying X2Go Servers' loads in regular intervals # @@ -294,13 +295,13 @@ # o the session profile does not block queries to the load checker daemon # on a per profile basis # -#default-use-load-checker = false +default-use-load-checker = true # If the x2gobroker-loadchecker daemon gets used, define here how # many seconds to sleep between cycles of querying system load from the # associated X2Go Servers. # -#load-checker-intervals = 300 +load-checker-intervals = 300 ### @@ -345,9 +346,8 @@ #desktop-shell = KDE [broker_inifile] -#enable = true -#session-profiles = /etc/x2go/broker/x2gobroker-sessionprofiles.conf -#use-load-checker = false +enable = true +session-profiles = /etc/x2go/broker/x2gobroker-sessionprofiles.conf #[broker_ldap] -> MUSIC OF THE FUTURE #enable = false # --------------------------------------------------------- # --------------------------------------------------------- diff -u /etc/x2go/broker/x2gobroker-sessionprofiles.conf.orig /etc/x2go/broker/x2gobroker-sessionprofiles.conf --- /etc/x2go/broker/x2gobroker-sessionprofiles.conf.orig 2016-03-19 19:19:33.995277777 +0100 +++ /etc/x2go/broker/x2gobroker-sessionprofiles.conf 2016-03-19 19:58:45.407309387 +0100 @@ -63,146 +63,12 @@ directrdp=false user=BROKER_USER -[localhost-kde] -name=KDE - localhost -host=localhost -command=KDE +[GloveBox] +host=firstnode (firstnodeip), secondnode (secondnodeip) +name=GloveBox +published=true usebrokerpass=true - -[localhost-mate] -name=MATE - localhost -host=localhost -command=MATE -usebrokerpass=true - -[localhost-shadow] -name=SHADOW - localhost -# don't even try load-balancing here... it makes not sense and won't work (first given host will be used!) -host=localhost -command=SHADOW -usebrokerpass=true - -### EXAMPLES: Below you find some config examples. Adapt them to your needs or -### simply write your own session profiles and remove the examples below. - -## -## EXAMPLE: pool-A (staff servers) -## -## The pool-A contains three X2Go Servers (server-A, server-B and server-C). - -## The staff of our example institute falls into two groups of users: -## gnome-users and kde-users. -## The gnome-users log into server-A or server-B, depending on their client -## subnet (IP configuration of the client). -## The kde-users login to server-C (server-C can be reached from the whole -## intranet). -## -## The client IP based split-up of the GNOME users allows some primitive load -## balancing. -## -## If staff people are members of both groups (kde-users, gnome-users) both -## session profiles will be shown in X2Go Client. -## - -#[pool-A-server-A] -#user= -#host=server-a.pool-a.domain.local -#name=GNOME - pool-A (srv-A) -#command=GNOME -#rootless=false -#acl-groups-allow=gnome-users,admins -#acl-groups-deny=ALL -#acl-clients-deny=ALL -#acl-clients-allow=10.1.0.0/16 -#acl-any-order=deny-allow -#broker-session-autologin=true - -#[pool-A-server-B] -#user= -#host=server-b.pool-a.domain.local -#name=GNOME - pool-A (srv-B) -#command=GNOME -#rootless=false -#acl-groups-allow=gnome-users,admins -#acl-groups-deny=ALL -#acl-clients-deny=ALL -#acl-clients-allow=10.2.0.0/16 -#acl-any-order=deny-allow -#broker-session-autologin=true - -#[pool-A-server-C] -#user= -#host=server-c.pool-a.domain.local -#name=KDE - pool-A (srv-C) -#command=KDE -#rootless=false -#acl-groups-allow=kde-users,admins -#acl-groups-deny=ALL -#acl-any-order=deny-allow -#broker-session-autologin=true - -## -## EXAMPLE: pool-B (e.g. webserver in the DMZ or on the internet) -## -## The pool-B is a single X2Go Server (server-D) that is -## hosted externally. The server-D has an official internet IP. -## -## The session profile for server-D shall be provided to the -## admins group only. -## -## Furthermore, the session profile for server-D shall only get -## offered to a member of the admins group if the admin is sitting -## in front of one of the admin client machines. -## - -#[pool-B-server-D-LXDE] -#user= -#host=server-d (server-d.domain.internet) -#name=LXDE - srv-D -#command=LXDE -#rootless=false -#acl-groups-allow=admins -#acl-groups-deny=ALL -## make sure hostnames in client ACLs are resolvable via libnss!!! -#acl-clients-deny=ALL -#acl-clients-allow=admin-machine1.domain.local, admin-machine2.domain.local, admin-machine3.domain.local -#acl-any-order=deny-allow - -## -## EXAMPLE: pool-C (REAL LOAD BALANCING!!!) -## -## The pool-C is a server pool for students. Our example institute -## knows 200-300 students and has to offer working places for -## every student. -## -## The resource limits on these servers are pretty strict, so staff members -## normally stay away from these machines, anyway. Only two test account -## get this session profile into their X2Go Clients. -## -## The pool-C contains 6 X2Go Servers that serve all students users together -## as a load balance server farm. The servers' hostnames are s-E1, s-E2, ... -## (as found in /etc/hostname). The hosts, however, are not configured in DNS -## so we give their IPs explicitly (also works for IPv6). -## -## Make sure to install x2gobroker-agent on all these 6 X2Go Servers. Also make -## sure to once run the script x2gobroker-keygen on the broker host and once -## the script x2gobroker-pubkeyauthorizer per X2Go Server. -## -## All 6 X2Go Servers have to be configured to use the PostgreSQL X2Go session -## DB backend. -## - -#[pool-C-XFCE] -#user= -#host=s-E1 (10.0.2.11),s-E2 (10.0.2.12),s-E3 (10.0.2.13),s-E4 (10.0.2.14),s-E5 (10.0.2.15) -#name=XFCE - pool-C -#command=XFCE -#rootless=false -#acl-users-allow=testuser-A,testuser-B -#acl-users-deny=ALL -#acl-groups-allow=students,admins -#acl-groups-deny=ALL -#acl-any-order=deny-allow # this server pool has a special broker setup for SSH authorized_keys -#broker-session-autologin=true -#broker-authorized-keys=/var/lib/x2gobroker/ssh/%u/authorized_keys +broker-session-autologin=true +broker-authorized-keys=/etc/ssh/authorized_keys.d/%u # --------------------------------------------------------- # --------------------------------------------------------- dpkg -l|grep x2go ii cups-x2go 3.0.1.3-0x2go1+git20160127.135+jessie.main.1 all Virtual X2Go printer for CUPS ii libnx-x11-6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 client-side library ii libnx-xcomposite1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Composite extension library ii libnx-xdamage1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 damaged region extension library ii libnx-xdmcp6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Display Manager Control Protocol library ii libnx-xext6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 miscellaneous extension library ii libnx-xfixes3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 miscellaneous 'fixes' extension library ii libnx-xinerama1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Xinerama extension library ii libnx-xpm4:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 pixmap library ii libnx-xrandr2:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 RandR extension library ii libnx-xrender1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Rendering Extension client library ii libnx-xtst6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Testing -- Record extension library ii libxcomp3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 compression library ii libxcompext3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 protocol compression extensions library ii libxcompshad3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 shadowing library ii nx-x11-common 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 all nx-X11 (common files) ii nxagent 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 NX agent ii python-x2gobroker 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (Python modules) ii x2go-keyring 2012.07.23~jessie~main~17~build1 all GnuPG keys of all X2Go developers and the X2Go archive ii x2goagent 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 all X2Go agent ii x2gobroker 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (executable) ii x2gobroker-agent 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 i386 X2Go Session Broker (remote agent) ii x2gobroker-authservice 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (PAM authentication service) ii x2gobroker-daemon 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (standalone daemon) ii x2goserver 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 i386 X2Go server daemon scripts ii x2goserver-extensions 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 all X2Go server daemon scripts (extensions) ii x2goserver-printing 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 all X2Go server daemon scripts (printing) ii x2goserver-xsession 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 all X2Go server daemon scripts (Xsession runner) # --------------------------------------------------------- cat /etc/apt/sources.list # Security Updates deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free # Backports deb http://ftp.debian.org/debian/ jessie-backports main contrib non-free # ClamAV etc. deb http://ftp.debian.org/debian jessie-updates main contrib non-free deb-src http://ftp.debian.org/debian jessie-updates main contrib non-free # Stable deb http://ftp.de.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.de.debian.org/debian/ jessie main contrib non-free # X2go Repository deb http://packages.x2go.org/debian jessie main # X2go Repository (sources) deb-src http://packages.x2go.org/debian jessie main # --------------------------------------------------------- # --------------------------------------------------------- cat /etc/debian_version 8.3 # --------------------------------------------------------- Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

3 10

Bug#1012: Session reconnect doesn't work (x2gobroker)
by Miguel Quero 07 Sep '18

07 Sep '18

I can confirm this bug, but the problem is not with all x2gobroker, the resume problem become when you use ssh broker. In my setup, when client connect with --broker-url=https://XXXX.XXXX.XXXX:8080/plain/inifile, all work fine and resume is working. But when same clients connect with same credentials to the same broker with x2goclient --broker-url=ssh://XXXX.XXXX.XXXX/usr/bin/x2gobroker --broker-autologin, all work fine but resume is not working, all connection open a new session :S. I cant debug with ssh broker :(. Any ideas? -- Miguel Quero | One eSecurity | www.one-esecurity.com M: +34 608 36 17 05 Europe (Spain): +34 911 011 000 PGP: 0x34AA 050B D15C 7593 5671 3748 40C6 8E95 6C5A 40D3

3 3

Heads-Up: X2Go: The Gathering 2018 (2018-11-09 - 2018-11-11) will very likely take place at Stuttgart's hackerspace "shackspace"
by Stefan Baur 30 Aug '18

30 Aug '18

Dear $ALL, since nobody has replied to the call for volunteers for the IT-Kongress event (see <https://www.mail-archive.com/x2go-project@lists.x2go.org/msg00278.html>), and since we've lost a sponsor, compared to the previous years, it is very likely that X2Go: The Gathering 2018 will have to take place at Stuttgart's hackerspace "shackspace" (<https://shackspace.de/>) - "will have to" meaning that we're out of suitable alternatives due to both time/volunteer staff as well as financial constraints. Thus, there will be no voting period regarding the location this year, we'll simply have to pick the only option that seems to be left at the moment. The last-resort fallback option would be Ulm's youth hostel (both as an event location as well as for sleeping arrangements), but this would mean groups of 4 people would have to share one room, as they do not offer smaller rooms - which, judging from previous years' feedback, is not a situation most of our participants would be happy with. This is why we're not offering a poll with Stuttgart and Ulm as options. For Stuttgart, we're looking at a hostel-like place that offers single and double rooms, as well as at a hotel nearby, for people that prefer a higher-quality sleeping arrangement. Details will be published on the Wiki at <https://wiki.x2go.org/doku.php/events:x2go-gathering-2018> as soon as the two sites have confirmed room availability and replied with their booking cancellation terms. Kind Regards, Stefan Baur (with my X2Go Event Planner hat on) -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

1 0

Bug#1323: SSH proxy connection doesn't work for tunnel only accounts
by Arcadie Cracan 21 Aug '18

21 Aug '18

Package: x2goclient Version: 4.1.2.1 Tag: patch I use a ssh proxy server that allows only tunnel connections (i.e. doesn't allow the users to use the shell). After upgrading from Ubuntu 16.04 to 18.04 x2goclient stopped working with my ssh proxy server. I believe the reason for this is the call to the "checkLogin()" function even for ssh proxy connections (which in my opinion is not necessary). I attach a patch that makes x2goclient skip the checkLogin() call (as it does for kerberos connections) for the ssh proxy connection. Thank you for considering this patch. Kind regards, Arcadie Cracan

1 0

Bug#1322: RFE: Allow setting nxagent nx/nx options on the server via x2goagent.options
by Orion Poplawski 20 Aug '18

20 Aug '18

Package: x2goserver Persion: 4.1.0.2 Tags: patch The attached patch allows the setting of nxagent nx/nx options on the server via x2goagent.options. Very useful for being able to set sleep=0. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

3 2

Bug#1280: Windows x2goclient 4.1.x crashes with Try Auto Login
by Ross Mohn 15 Aug '18

15 Aug '18

Package: x2goclient (Windows) Version: 4.1.x Reproduced with x2goclient-4.1.0.0-2017.03.11-setup.exe and x2goclient-4.1.1.1-2018.03.01-setup.exe Noticed this about a year ago, but didn't debug at that time and just fell back to 4.0.x version. Setup: pagent.exe running with correct id_rsa.ppk SSH key. Check the "Try auto login" box in the session preferences. Launch x2goclient.debug.exe (v4.1.1.1): x2go-INFO-1> "Starting X2Go Client..." x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." x2go-INFO-3> "Started X2Go Client." Process Explorer shows the following processes started, roughly in this order: x2goclient.debug.exe x2gohelper.exe sshd.exe pulseaudio.exe conhost.exe Click to launch the Session: x2go-INFO-8> "Starting connection to server: example.com:922" QObject::killTimers: timers cannot be stopped from another thread Process Explorer shows the following processes killed, roughly all at once: x2goclient.debug.exe x2gohelper.exe sshd.exe pulseaudio.exe conhost.exe Work arounds: 1) roll back to v4.0.x 2) uncheck the "Try auto login" box" and live with typing in your password. Thanks -Ross -- Ross Palmer Mohn rpmohn(a)waxandwane.org

2 1

Bug#1280: Resolved
by Ross Mohn 15 Aug '18

15 Aug '18

Installed x2goclient-4.1.2.0-2018.06.22 and performed additional testing. It seems that if I specify a key in the "Use RSA/DSA key for ssh connection" the client doesn't attempt to use the ssh agent at all, only that specific key file. I had thought that it would still try the agent first, but it only tries the specified key file and then moves right to asking for the password, skipping the agent altogether. Next I created a new id_ed25519.ppk file and loaded it with pagent. I leave "Use RSA/DSA key for ssh connection" blank. The client now immediately uses pagent for authentication and launches my session without requiring any further interaction. OK to close, thanks! -Ross

2 1

Bug#1319: PulseAudio does not start
by SW＠EU 14 Aug '18

14 Aug '18

Package: mingw32-pulseaudio Version: 7.1 Hi, Windows 10 forced update to 1803 (Pro edition, englisch + German language pack) and x2goclient updated using x2goclient-4.1.2.0-2018.06.22-setup.exe. Since that I have to disable Pulse-Audio because otherwise I get the attached error during any start of the client. I have in meantime uninstalled the the separate installed 64 Bit VcXsrv because the 32 Bit x2goclient installation has changed files in the 64 Bit VcXsrv installation (is this correct?) and uninstalled x2goclient, rebooted, x2goclient again installed but 64 Bit VcXsrv not again, rebooted, but still the same. TIA, Silvio

1 0

Bug#1317: extended checks for loadchecker (or broker ... dunno)
by Walid MOGHRABI 13 Aug '18

13 Aug '18

package: x2gobroker version: 0.0.4.0-0~1038~ubuntu16.04.1 priority: enhancement We encountered another corner case very annoying. The whole broker stack does its work quite well when everything works as expected (which is mostly the case). A failing server for example is perfectly handled, loadchecker simply disable this server from the list and thus, broker sends users to remaining live servers. Problems are beginning when your servers misbehaves. Loadchecker mainly checks : * liveness ("ping") * ssh acess * load/memory values This is okay but not enough to be sure that a server can handle incoming connections, for example, for our needs, we should make sure that : * a user can authenticate on a server (Active Directory authentication through PAM/Winbind) * some mounts are correct (/home folders, other user mounts or shares) * some networks are available * some mandatory services are running * ... In our recent problems, for unknown reasons, some servers were having troubles joining the Active Directory domain and thus, user auth was failing. On the broker/loadchecker side, the server is perfectly working and this is even one of the best performing server since it is empty so it allways tries to redirect incoming connections to this server and since users can't auth, it fails and blocks every new connections. With extended checks, this server would have been considered offline from the loadchecker point of view and thus, it would have just been out of the load balancing. Since those checks are pretty "specific", it would be great to have some kind of "extended check" feature where a directory "extra-check.d" folder would exist on the x2gobroker setup in which we could drop some scripts that would be executed by the x2gobroker user on the remote servers with just an "ok" or "ko" value. As soon as you get a "ko" value, the server would be considered unavailable and then removed from load balancing until the next "ok" check. Script could be of any language with supported intepreter installed on the server (could be bash, perl, python or anything, you'll just need the interpreted to be installed but this is the administrator responsibility). --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev August 2018