x2go-dev May 2018

x2go-dev@lists.x2go.org

16 participants
107 discussions

Bug#1171: Create wtmp entry for x2go sessions
by Orion Poplawski 19 Nov '18

19 Nov '18

Package: x2goserver Version: 4.1.0.0 Severity: wishlist X2Go should write an entry to /var/run/utmp and /var/log/wtmp. This would allow currently logged inn users to be seen in the output of 'w', and 'last' would also list previous sessions. This could be done via either libutempter or vte. -- Orion Poplawski Technical Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

2 1

Bug#839: fqdn hostnames in load_factors
by Sergey Savko 13 Sep '18

13 Sep '18

Package: python-x2gobroker Version: 0.0.3 Severity: normal In massive load_factors.keys variable busy_server = test-001.tophouse.local In massive busy_servers_temp.keys variable busy_server = test-001 As a result, I get garbage. -- Yours truly, Sergey Savko.

2 2

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

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#1034: Fix a segfault in x2goclient with OpenBSD
by Denis Fondras 26 May '18

26 May '18

Event better patch from Jeremie on OpenBSD mailing-list : https://marc.info/?l=openbsd-ports&m=146327448112980&w=2

2 1

Bug#1226: x2goclient for Mac OS immediately throws error regarding "PulseAudio verison number" then crashes
by Sean Hooten 26 May '18

26 May '18

Package: X2GoClient_latest_macosx_10_9 Version: 4.1.0.0 Steps taken to produce the bug: Ran x2goclient.app, immediately get error upon initialization. Exact error message: > Error fetching PulseAudio version number! Unexpected format encountered. Expected: I expected x2goclient to initialize normally without an error message. What actually happened: x2goclient shows me the regular user interface with the pop-up error message. After selecting "Okay" it crashes. This was not an issue before, seemingly began happening spontaneously. I have attempted to reboot my machine, and reinstalled x2goclient and XQuartz to no avail. I have attached the full bug report. I'm not sure why it is attempting to fetch a PulseAudio version number, this is not on my machine and I had not yet attempted to connect to my server before receiving the error. OS: Mac OS X 10.11.6 Thanks! Sean

4 14

Getting suspended session profile info through X2GoClient API
by Tomáš Cerha 25 May '18

25 May '18

Dear list, I am using the X2Go Python API to develop a custom UI for running our applications from (mainly) Windows client machines. When starting an application based on a session profile obtained from the X2Go broker, I am checking for the suspended sessions on the server by calling X2GoClient.list_sessions(). X2GoClient.list_sessions() returns the list of all sessions on the server, including also sessions of other profiles. I need to filter them out to include only the sessions of the same profile, which is currently starting. The X2GoSessionInfo instances, however, don’t include the information I need. I need the profile name, profile id or at least the command. The command is included in the session name, but I don’t feel that parsing the session name is the right way to go. Thus I tried to obtain more information about the session using X2GoClient.get_session_of_session_name(), but it returns None for all session names returned by X2GoClient.list_sessions(). I also tried to pass profile_name or profile_id to X2GoClient.list_sessions() but it is probably not meant to filter the sessions as I am still receiving the complete list of sessions including also sessions of other profiles. So is there a way to find out the profile name, profile id or command of a suspended session returned by X2GoClient.list_sessions()? Thank you for any advice. Best regards Tomas Cerha

2 5

Subscription information regarding x2go-dev - please read
by Mike Gabriel 24 May '18

24 May '18

Dear Subscriber, As the regulations of the GDPR <https://gdpr-info.eu/> are becoming effective on May 25, 2018, we would like to send you a quick reminder about your subscription to the mailing list named x2go-dev HERE'S WHAT YOU NEED TO DO NOW You need to read this entire message. No further action will be required on your part, unless after reading, you don't want to be subscribed any longer - in that case, please follow the instructions below. HERE'S HOW TO REVIEW YOUR SETTINGS You may review your account settings at any time, and unsubscribe, should you ever wish to, by going to <https://lists.x2go.org/listinfo/x2go-dev> HERE'S WHY WE BELIEVE WE MAY SEND YOU LIST E-MAILS As we have sufficient reason to believe that you personally signed up, due to us using a two-step (AKA "double opt-in") subscription process, an active subscription will be taken as consent in the sense of Article 6 (1) a) and Article 7 (1) of the GDPR. HERE'S HOW TO UNSUBSCRIBE You have the right to withdraw your consent at any time, thus ending your subscription, as per Article 7 (3) of the GDPR. To do so, please unsubscribe using the link above. To protect against accidental or "hostile" unsubscribing, a two-step process is also used to handle unsubscribe requests. HERE'S WHAT TO DO IF YOU ENCOUNTER PROBLEMS UNSUBSCRIBING If you have difficulties unsubscribing, because the E-Mail with the unsubscribe link isn't showing up in your E-Mail inbox, please, first check your SPAM folder for any messages our list server may have been trying to send you; if nothing shows up there either, please contact the list administrators at: <mailto:x2go-dev-owner@lists.x2go.org> HERE'S HOW WE HANDLE YOUR E-MAIL ADDRESS DATA Please understand that we need to keep your E-Mail address stored in our database for the duration of your subscription, which is a justifiable cause as set forth in Article 6 (1) b) of the GDPR. Your E-Mail address will be deleted from the distribution list automatically and immediately upon unsubscribing, and may be blacklisted (thus stored permanently, but blocked from receiving messages) either on your request, or if we notice abuse stemming from your address. Your E-Mail address is not shared with others, unless you actively post to the list. If you do, it will become visible to all other subscribers, and it may also become visible in part or fully on web sites that offer a public archive of mailing list posts, as well as in our own archive, which you can find here: <http://lists.x2go.org/pipermail/x2go-dev> If you want to keep your real E-Mail address secret from the public, while remaining subscribed, we suggest you either refrain from posting, or subscribe with a temporary, "burner" E-Mail address you created specifically for that purpose. HERE'S HOW TO REQUEST MESSAGE DELETION If you believe an E-Mail you sent should be purged from the public archive that we operate (see the link above), please also contact the list administrators at <mailto:x2go-dev-owner@lists.x2go.org> Note that list administrators have no influence what other recipients of the particular list message do with it - e.g. if others choose to mirror contents of our list archive on their own web site, you will need to contact them separately with your deletion request. Thank you for taking the time to read this far, and for being a subscriber. Have a nice day.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev May 2018