x2go-user October 2014

x2go-user@lists.x2go.org

36 participants
41 discussions

client side printing
by Bernhard J. Mayr 27 Oct '14

27 Oct '14

I am having big trouble administering client side print functionality. I have installed the x2go print package on the server. The user is in the fuse group and there is a spool-dir mounted. In the X2Go Client I configured client side printing. bmayr@127.0.0.1:/home/bmayr/.x2go/S-root-50-1413989095_stDLXDE_dp24/spool on /tmp/.x2go-root/spool/C-root-50-1413989095_stDLXDE_dp24 type fuse.sshfs (rw,nosuid,nodev,default_permissions) When I start a print job, nothing happens. The cups-access log says: localhost - - [22/Oct/2014:17:03:01 +0200] "POST /printers/Virtual_X2Go_Printer HTTP/1.1" 200 21992 Print-Job successful-ok Any ideas what I can do to enable client side printing? Thankfully Yours, -- ########################################################## Preisträger Constantinus-Preis 2012 Nutzen Sie auch unsere Apps für Android: Übersicht über alle deutschen ICD10-Codes: https://play.google.com/store/apps/details?id=net.eaustria.icd10.release Alle Arzneimittel und Medikamenten direkt am Smartphone: https://play.google.com/store/apps/details?id=net.eaustria.eaustria_medicat… ########################################################## Dr. Bernhard J. Mayr, MBA Projektkoordinator elexis-austria | Freie Software für freie Berufe Tulpenweg 10 4600 Wels, Austria Tel.: +43(0)660 31 96 763 E-Mail: bernhard.mayr(a)elexis-austria.net www: www.elexis-austria.net www: www.arztsoftware.it fb: www.facebook.com/elexis-austria youtube: www.youtube.com/elexisaustria

3 3

Re: [X2Go-User] man page update X2Go Client
by Mike Gabriel 27 Oct '14

27 Oct '14

Hi Robert, (Re-Cc:ing x2go-user ML) On So 26 Okt 2014 23:37:04 CET, nanook wrote: > Hi, very clean, nice that you include examples. Curious why -user > is only available with LDAP and not other directory services such as NIS? X2Go Client has its own LDAP backend, very like to the usage of an LDAP address book. If the servers use libnss-ldap(d) or the NIS functionality in basic libnss is not related to when written "X2Go Client in LDAP mode". Unfortunately, the public documentation for X2Go Client in LDAP is very scarce and I have neither tested it so far. Greets, 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

Help requested to debug kde session failure
by Roderick Johnstone 23 Oct '14

23 Oct '14

Hi I need some help debugging my failing x2go sessions please. Client is v4.0.2.1 on OSX Mavericks. Server is 4.0.1.18 on Fedora 20. This is one of Orion's builds for Fedora. I've been using server version 4.0.1.15 for some time, but its a bit flakey in the sense that often it is not easy to reconnect to a session, ie it takes several attempts or the session must be killed and started a fresh. I was trying to see whether the 4.0.1.18 server would fix this issue but it seems to have bigger problems for me. What works is: 1) Connecting to another Fedora 20 system running v4.0.1.15 server on with a KDE session but with the problem of not being able to resume sessions reliably. 2) Connecting to the 4.0.1.18 x2goserver with a single terminal session. What fails is: Connecting to the 4.0.1.18 x2goserver with a KDE session. I get no session at all, and in the client window I get a message simliar to "your connection was closed before it got into a usable state". The connection dialogue disappears before I can read it all, and I can't see where it is saved. In /tmp/.x2go-rmj/C-rmj-159-1414083481_stDKDE_dp32: the state file says STARTING the cmdoutput file says: exec startkde Output of session.log is appended at the bottom. There is more debug info available from /var/log/messages from having set loglevel debug in /etc/x2go/x2goserver.conf which I'm happy to share off line. I've tried setting full debugging in kdebugdialog but nothing at all was logged to ~/.xsession-errors. I'd appreciate any pointers to how to debug this further. I can, of course, log in a KDE session on the console of the system running the 4.0.1.18 server and a simple x2go session running only the Terminal appliation works too on that server. Thanks Roderick session.log Running as X2Go Agent NXAGENT - Version 3.5.0 Copyright (C) 2001, 2011 NoMachine. See http://www.nomachine.com/ for more information. Info: Agent running with pid '16334'. Session: Starting session at 'Thu Oct 23 17:58:02 2014'. Info: Proxy running in server mode with pid '16334'. Info: Waiting for connection from 'localhost' on port '30331'. Info: Accepted connection from '127.0.0.1'. Info: Connection with remote proxy completed. Info: Using ADSL link parameters 512/24/1/0. Info: Using agent parameters 5000/10/50/0/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 4/4. Info: No suitable cache file found. Info: Listening to X11 connections on display ':159'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-rmj/C-rmj-159-1414083481_stDKDE_dp32/options:159''. Session: Aborting session at 'Thu Oct 23 17:58:03 2014'. Session: Session aborted at 'Thu Oct 23 17:58:03 2014'. Warning: Signals were not blocked in process with pid '16334'. Info: Waiting the cleanup timeout to complete.

1 0

x2go 4.0.3.0.client for OSX
by Roderick Johnstone 22 Oct '14

22 Oct '14

Hi I was looking for the recently announced x2go v4.0.3.0 client for OSX at http://code.x2go.org/releases/binary-macosx/x2goclient/releases/ but the latest there is 4.0.2.1 dated 21 Oct 09:29. Does this directory take a while to sync up with releases or am I looking in the wrong place? I notice that the heuler directory has 4.0.3.0 subdirectory with a 4.0.3.0 x2goclient dmg. Thanks Roderick

5 5

restricting access to published applications
by Bernhard J. Mayr 22 Oct '14

22 Oct '14

Hi! Is there a chance to restrict access to x2go server to only published applications sessions in the way that a user can only establish x2go "published applications" sessions but no desktop session? Thankfully Yours! Bernhard -- ########################################################## Preisträger Constantinus-Preis 2012 Nutzen Sie auch unsere Apps für Android: Übersicht über alle deutschen ICD10-Codes: https://play.google.com/store/apps/details?id=net.eaustria.icd10.release Alle Arzneimittel und Medikamenten direkt am Smartphone: https://play.google.com/store/apps/details?id=net.eaustria.eaustria_medicat… ########################################################## Dr. Bernhard J. Mayr, MBA Projektkoordinator elexis-austria | Freie Software für freie Berufe Tulpenweg 10 4600 Wels, Austria Tel.: +43(0)660 31 96 763 E-Mail: bernhard.mayr(a)elexis-austria.net www: www.elexis-austria.net www: www.arztsoftware.it fb: www.facebook.com/elexis-austria youtube: www.youtube.com/elexisaustria

2 2

Re: [X2Go-User] x2go-user Digest, Vol 6, Issue 19
by Tom McManus 22 Oct '14

22 Oct '14

Where do I download x2goclient-4.0.1.6-20141019.dmg? -- Tom McManus (http://help.nmr.mgh.harvard.edu) On Tue, 21 Oct 2014 12:00pm, x2go-user-request(a)lists.x2go.org wrote: > Send x2go-user mailing list submissions to > x2go-user(a)lists.x2go.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.x2go.org/listinfo/x2go-user > or, via email, send a message with subject or body 'help' to > x2go-user-request(a)lists.x2go.org > > You can reach the person managing the list at > x2go-user-owner(a)lists.x2go.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of x2go-user digest..." > > > Today's Topics: > > 1. Changing the X2Go Client for Windows version numbering > (Michael DePaulo) > 2. Re: Changing the X2Go Client for Windows version numbering > (James M. Pulver) > 3. Re: Mac OS X 10.10 (Yosemite) X2Go client (Mike Gabriel) > 4. Re: Mac OS X 10.10 (Yosemite) X2Go client (Ricardo D?az Mart?n) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 20 Oct 2014 08:16:21 -0400 > From: Michael DePaulo <mikedep333(a)gmail.com> > To: "x2go-user(a)lists.x2go.org" <x2go-user(a)lists.x2go.org> > Subject: [X2Go-User] Changing the X2Go Client for Windows version > numbering > Message-ID: > <CAMKht8hnGJA5+QbP-zz9QU5PUpTTMm3T-qFdqg5p-qkG_oHRNg(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > X2Go Users, > > I'd like feedback on this topic. > > I am thinking of switching the X2Go Client for Windows version > numbering over to the version numbering that X2Go Client for Mac OS X > uses such as: > If X2Go Client for Windows 4.0.3.0 were released today: > 4.0.3.0-20141020 > If I had to make any sort of change, either in the build process or in > the source code, on 2014-11-21: > 4.0.3.0-20141121 > > The reason for this change is that I believe these version numbers > will be simpler and less confusing. This would be especially true for > Windows users who are not used to the version numbering used by Linux > distros. > > Under the current version numbering , if I were to build X2Go Client > for Windows 4.0.3.0 when it is released the version number would > simply be: > 4.0.3.0 > Then say I had to make 2 changes to the build process, such as calling > different commands during the build process or bundling different 3rd > party binaries/libraries (e.g., VcXsrv, OpenSSL). The 2 new version > numbers would be: > 4.0.3.0+build1 > 4.0.3.0+build2 > If I had to then make a change to the source code, it would be: > 4.0.3.0+hotfix1 > And if I had to make 2 more changes to the build process, the 2 new > version numbers would be: > 4.0.3.0+hotfix1+build1 > 4.0.3.0+hotfix1+build2 > > -Mike#2 > > > ------------------------------ > > Message: 2 > Date: Mon, 20 Oct 2014 12:27:40 +0000 > From: "James M. Pulver" <jmp242(a)cornell.edu> > To: "x2go-user(a)lists.x2go.org" <x2go-user(a)lists.x2go.org> > Subject: Re: [X2Go-User] Changing the X2Go Client for Windows version > numbering > Message-ID: > <981ce53b33b44aa89d78c6107bbac2eb(a)BY2PR04MB775.namprd04.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > Personally, I don't love either build numbering method. That said, I find the date suffix much harder to parse personally, it's too many numbers munged together and I just end up ignoring it. > > What do you all mean by the numbering anyway - i.e. why would > 4.0.3.0+hotfix1 > Not be 4.0.3.1? > > Personally, from a Windows admin / user perspective, I don't care what the build process is in terms of a binary I download. I care if something changed. > > So if 4.0.3.0+build1 changed the version of gcc but didn't change the output, I doubt anyone would care - maybe somewhere would be a build # for deep debugging, but it wouldn't be in any download name someone would use. > > If 4.0.3.0+build2 packaged a new library that fixed a bug, I'd expect to see > 4.0.3.1 again as it fixed something "in the product" from my perspective. > > I'm a fan of MajorChange.MinorFeatureChange.Bugfix.someotherchange sort of software numbering. > > That all said - I would like to see the numbering be consistent across platforms in terms of code that is shared, and the method also be consistent. > -- > James Pulver > CLASSE Computer Group > Cornell University > > > -----Original Message----- > From: x2go-user-bounces(a)lists.x2go.org [mailto:x2go-user-bounces@lists.x2go.org] On Behalf Of Michael DePaulo > Sent: Monday, October 20, 2014 8:16 AM > To: x2go-user(a)lists.x2go.org > Subject: [X2Go-User] Changing the X2Go Client for Windows version numbering > > X2Go Users, > > I'd like feedback on this topic. > > I am thinking of switching the X2Go Client for Windows version numbering over to the version numbering that X2Go Client for Mac OS X uses such as: > If X2Go Client for Windows 4.0.3.0 were released today: > 4.0.3.0-20141020 > If I had to make any sort of change, either in the build process or in the source code, on 2014-11-21: > 4.0.3.0-20141121 > > The reason for this change is that I believe these version numbers will be simpler and less confusing. This would be especially true for Windows users who are not used to the version numbering used by Linux distros. > > Under the current version numbering , if I were to build X2Go Client for Windows 4.0.3.0 when it is released the version number would simply be: > 4.0.3.0 > Then say I had to make 2 changes to the build process, such as calling different commands during the build process or bundling different 3rd party binaries/libraries (e.g., VcXsrv, OpenSSL). The 2 new version numbers would be: > 4.0.3.0+build1 > 4.0.3.0+build2 > If I had to then make a change to the source code, it would be: > 4.0.3.0+hotfix1 > And if I had to make 2 more changes to the build process, the 2 new version numbers would be: > 4.0.3.0+hotfix1+build1 > 4.0.3.0+hotfix1+build2 > > -Mike#2 > _______________________________________________ > x2go-user mailing list > x2go-user(a)lists.x2go.org > http://lists.x2go.org/listinfo/x2go-user > > > ------------------------------ > > Message: 3 > Date: Tue, 21 Oct 2014 07:29:27 +0000 > From: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> > To: Ricardo D?az Mart?n <ricardo.diaz(a)oceanosoft.com> > Cc: x2go-user(a)lists.x2go.org > Subject: Re: [X2Go-User] Mac OS X 10.10 (Yosemite) X2Go client > Message-ID: > <20141021072927.Horde.2ismKJ5MkdR9q5FJX70Shw1(a)mail.das-netzwerkteam.de> > > Content-Type: text/plain; charset="utf-8"; Format="flowed"; > DelSp="Yes" > > Hi Ricardo, > > On Di 21 Okt 2014 07:54:51 CEST, Ricardo D?az Mart?n wrote: > >> Hi Mike, >> >> I got some users updated to Yosemite. Could you send to me or upload to the >> releases the .dmg Yosemite compatible. >> >> Regards, >> >> -- >> <ricardo.diaz(a)oceanosoft.com> > > The Yosemite fix is now available in x2goclient-4.0.1.6-20141019.dmg [1]. > > Sorry for the delay! > Mike > > [1] > http://code.x2go.org/releases/binary-macosx/x2goclient/releases/4.0.2.1/x2g… > > -- > > 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… >

3 4

Security setup on server with x2go
by Hanák 22 Oct '14

22 Oct '14

Hello, I would like to ask experienced users, how they solve security topics on their x2go servers. I have the server where users are allowed to start only very a limited set of commands through ssh. I am using sshd_config option ForceCommand which allows to start only /usr/local/bin/check_ssh_cmd where I test SSH_ORIGINAL_COMMAND. Everything works fine so far. Now I need to allow users to start also some commands through x2goclient. The problem is that in order x2go to work I need to allow also every single command which is sent by x2goclient. I tried to track what is being sent and there are a lot of commands like 'sh -c "echo X2GODATABEGIN: ... echo X2GODATAEND"'. So the question is, how to write the rules in check_ssh_cmd wrapper script. If I would allow any command containing X2GODATABEGIN and X2GODATAEND, it would probably work, but my security setup of ssh would be broken, because somebody who knows, how x2go internally works, could sent his own commands wrapped in X2GODATABEGIN and X2GODATAEND. What would you recommend? Any sugestions are appreciated. Pavel

1 0

x2go sessions
by Magnus Hagdorn 22 Oct '14

22 Oct '14

Hi there, is there a way I can limit the session types I offer to x2go clients? I would like to stop users from using gnome/kde sessions and get them to use icewm instead. I do realise that if they know how to they could simply execute the relevant session program directly. I'd just like to make the default session sane. Cheers magnus -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

2 1

X2Go Server / X2Go Client with openSSH 6.7 (Debian jessie et al.)
by Mike Gabriel 21 Oct '14

21 Oct '14

Hi all, openSSH 6.7 has just entered Debian unstable and will be in Debian jessie soon. It will probably land in other distributions rather sooner than later. As the openSSH developers have--by default--disabled several kex algorithm in the latest openSSH 6.7 release, X2Go Client on older systems (Debian wheezy, Ubuntu 14.04, etc.) will fail connecting to those machines. """ (This probably is the error message X2Go Client shows on your screen...) X2Go Client reports: kex error : did not find one of algos diffie-hellman-group1-sha1 in list curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 for kex algos """ The issue can be addressed in two ways... OPTION 1: --------- If you only have control of the client, you may get the issue resolved by backporting a libssh 0.6.3 version. Consult your distribution's build tools to make this happen. I will checkout what we as X2Go upstream can provide for you in our package repositories without breaking other parts of your system (older applications using libssh << 0.6.0 are very likely to break with that newer libssh). OPTION 2: --------- If you have control of the server, then you may want to re-enable the mode-insecure, older, by-default-disabled algos. From the sshd_config man page in openSSH 6.7: """ KexAlgorithms Specifies the available KEX (Key Exchange) algorithms. Multiple algorithms must be comma-separated. The supported algorithms are: curve25519-sha256(a)libssh.org diffie-hellman-group1-sha1 diffie-hellman-group14-sha1 diffie-hellman-group-exchange-sha1 diffie-hellman-group-exchange-sha256 ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 The default is: curve25519-sha256(a)libssh.org, ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha1 """ What you probably have to add to the KexAlgorithms parameter in /etc/ssh/sshd_config are these additional algos: diffie-hellman-group1-sha1 and diffie-hellman-group-exchange-sha1. """ KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521 """ If you use the KexAlgorithms option in sshd_config, make sure that you: o also add all the default algos o restart openSSH server on your server and try a second login while you are still logged in with another session (in case you broker something by editing sshd_config) Greets, 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 1

Changing the X2Go Client for Windows version numbering
by Michael DePaulo 21 Oct '14

21 Oct '14

X2Go Users, I'd like feedback on this topic. I am thinking of switching the X2Go Client for Windows version numbering over to the version numbering that X2Go Client for Mac OS X uses such as: If X2Go Client for Windows 4.0.3.0 were released today: 4.0.3.0-20141020 If I had to make any sort of change, either in the build process or in the source code, on 2014-11-21: 4.0.3.0-20141121 The reason for this change is that I believe these version numbers will be simpler and less confusing. This would be especially true for Windows users who are not used to the version numbering used by Linux distros. Under the current version numbering , if I were to build X2Go Client for Windows 4.0.3.0 when it is released the version number would simply be: 4.0.3.0 Then say I had to make 2 changes to the build process, such as calling different commands during the build process or bundling different 3rd party binaries/libraries (e.g., VcXsrv, OpenSSL). The 2 new version numbers would be: 4.0.3.0+build1 4.0.3.0+build2 If I had to then make a change to the source code, it would be: 4.0.3.0+hotfix1 And if I had to make 2 more changes to the build process, the 2 new version numbers would be: 4.0.3.0+hotfix1+build1 4.0.3.0+hotfix1+build2 -Mike#2

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user October 2014