x2go-dev December 2015

x2go-dev@lists.x2go.org

15 participants
123 discussions

Central Settings for X2Go Client
by Oleksandr Shneyder 14 Dec '15

14 Dec '15

Hi All, there is a new feature in X2Go Client called "Central Settings". With this feature you can control X2Go Client settings for all users on machine in one place. The Client settings could be stored in /etc/x2goclient/config on Linux and Mac and in HKEY_LOCAL_MACHINE\\SOFTWARE\\x2goclient\\config on Windows. if this directory/regkey exists, X2Go Client will read settings from /etc/x2goclient/config/$USER on Linux/Mac and from HKEY_LOCAL_MACHINE\\SOFTWARE\\x2goclient\\config\\%USERNAME% on Windows. if this directory/key not exists, client will read settings from /etc/x2goclient/config/All Users and HKEY_LOCAL_MACHINE\\SOFTWARE\\x2goclient\\config\\All Users Format of the settings is same as in normal mode and could be easily copied from user directory or exported from Windows registry. in "Central Settings" mode all configuration and sessions editing will be disabled for user. Command line options will be also ignored. You can specify new command line parameters separated by semicolon in the "settings" config file. For example for Linux: $cat /etc/x2goclient/config/alex/settings: [General] commandline="--broker-url=ssh://broker/broker.pl;--maximize" for Windows: HKEY_LOCAL_MACHINE\\SOFTWARE\\x2goclient\\config\\alex\\settings commandline --broker-url=ssh://broker/broker.pl;--maximize this feature will be available from "nightly builds" soon. regards, Alex -- ----------------------------------------------------------- Oleksandr Shneyder | Email: o.shneyder(a)phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Ludwig-Feuerbach-str. 18 | Fax. : 0911 - 14870374 9 D-90489 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 -----------------------------------------------------------

1 0

Bug#971: Unable to restore session with AD login
by Dario Pilori 04 Dec '15

04 Dec '15

Package: x2goserver Version: 4.0.1.19 Hello We are using x2goserver on a Ubuntu 14.04 server, which is member of an AD domain. Users have usernames like "DOMAIN\user". After closing bug #664, users can successfully connect to x2goserver, but they cannot resume a suspended session. Every time the same user connects, x2go opens a new session. Logging in as a regular user via SSH, typing x2golistsessions does not return any output, even if the user has several sessions open. If root runs x2golistsessions_root, it displays all sessions, but in the username field of the table it is displayed the user as "DOMAINuser", without the backslash \. Using PostgreSQL database as a backend instead of SQLite3 fixes the problem. Best regards, Dario

1 0

Re: [X2Go-Dev] [X2Go-User] Global ssh-agent
by Orion Poplawski 03 Dec '15

03 Dec '15

On 12/01/2015 12:34 AM, Dmitry Bely wrote: > Hi Orion, > > On Thu, Nov 26, 2015 at 2:11 AM, Orion Poplawski <orion(a)cora.nwra.com> wrote: >> On 11/24/2015 05:10 AM, Dmitry Bely wrote: >>> Hi, >>> >>> I would like to use ssh-agent globally for X session (Debian/MATE if >>> it matters). X session starts it itself and when I login to X locally >>> it works as expected (SSH_AGENT_PID and SSH_AUTH_SOCK environment >>> variables are set correctly). But if I connect to the host via x2go, >>> strange things happen: in any terminal session SSH_AUTH_SOCK points to >>> non-existing path and SSH_AGENT_PID is not set at all. I tried to work >>> around this adding to ~/.bashrc: >>> >>> if [ ! -S ~/.ssh/ssh_auth_sock ]; then >>> eval `ssh-agent -s` >>> ln -sf "$SSH_AUTH_SOCK" ~/.ssh/ssh_auth_sock >>> fi >>> export SSH_AUTH_SOCK=~/.ssh/ssh_auth_sock >>> >>> This way SSH_AUTH_SOCK is correct but SSH_AGENT_PID is surprisingly >>> unset somethere. Any idea how to fix that? >>> >> >> I don't quite follow what you mean by "globally". Are you using >> desktop-sharing and connecting to an existing X session and want to use that >> ssh-agent? > > I need one ssh-agent per X session that all child processes can access. > >> In that case perhaps your x2go ssh connection is forwarding the >> ssh-agent connection from the client machine and you need to disable the agent >> forwarding. > > Probably you are right. But how to disable it in QT4 x2goclient? If I add > > Host * > ForwardAgent no > > to ~/.ssh/config it affects a separate ssh session but not > x2goclient's one. And I failed to find any command line/GUI x2goclient > option that is related to ssh agent forwarding. Hmm, it appears that the code never calls ssh_options_parse_config(), whether by intention or not I do not know. CCing the dev list to get their take on it. But the libssh docs indicate that it should be called: http://api.libssh.org/master/group__libssh__session.html#ga7a801b85800baa3f… And I can confirm that x2goclient does appear to forward the SSH_AGENT at least if using the ssh-agent for authentication to the remote server. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion(a)cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev December 2015