[X2Go-User] Broker and resuming sessions

[David Barron]

I just realized, on the login server there is no authorized_keys file in /var/lib/x2gobroker/.ssh, but it is on all 3 of the application servers.


David Barron
Zencos Consulting LLC
david.barron at zencos.com
919-480-2761 (office)
919-995-2356 (mobile)

-----Original Message-----
From: Stefan Baur <X2Go-ML-1 at baur-itcs.de> 
Sent: Wednesday, October 31, 2018 4:23 PM
To: David Barron <DBarron at zencos.com>; x2go-user at lists.x2go.org
Subject: Re: [X2Go-User] Broker and resuming sessions

Am 31.10.18 um 21:10 schrieb David Barron:


> Yes, is the problem also present when you try to use the broker via SSH instead of HTTP?
> I don't know, I've never been able to figure out how to use ssh.  The documentation on that is sparse.

That's why we have the Demo environment install scripts, where you get a fully configured setup from which you can copy settings/configs.

E.g.
<https://wiki.x2go.org/doku.php/doc:howto:x2gobroker?do=export_code&codeblock=9>
creates two desktop entries on the demo client, one for the HTTP, one for the SSH broker access.
See the section below
"COMMENT: This last step creates an X2GoClient-in-Broker-Mode desktop entry"

As you can tell from there, the ssh broker URL would be something like ssh://x2gobroker1.x2go.example.com:/usr/bin/x2gobroker-ssh


> Did you run x2gobroker-keygen on the broker server?
> Yes.  Should I run it again?

At the moment, it doesn't sound like you should.


> Did you invoke x2go-pubkeyauthorizer with the proper parameters on all required machines?  If so, you should have the same authorized_keys file in /var/lib/x2gobroker/.ssh/ on the three servers as well as on the broker.
> Yes.

Did you compare the content of the files, or merely verify their existence?


> Should I run it again?  Again, the documentation is sparse, so what parameters would I use?
If the files all have the identical content, no.

If they differ, copy /var/lib/x2gobroker/.ssh/authorized_keys from the broker to the three X2Go servers, that should keep you from having to re-run the command.

Also, please run

x2goclient --debug >x2goclientlog 2>&1

when you try to connect to the suspended session.

Make sure x2goclientlog doesn't contain any information you don't want us to see (i.e. if necessary, replace IPs with dummy IPs, same goes for usernames and passwords that might show up - though passwords shouldn't be visible there), then post the content of the file here.

-Stefan

--
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