[X2Go-User] ssh connection through bastion host

Hauke Fath hf at spg.tu-darmstadt.de
Thu Jun 27 10:49:48 CEST 2024


On Wed, 26 Jun 2024 23:50:45 +0200, Ulrich Sibiller wrote:
> the x2go is using libssh, which _partly_ reads your openssh config
> files. It understands _some_ of the options, but not all.

So I've read. What I have not been able to find, is information on what 
subset of the ssh_config(5) options libssh (and, in particular, the 
libssh version built into the x2go mac client) recognizes. Do you know 
more?
 
> You can use your ProxyJump setup in conjunction with -L to establish a
> port forwarding outside x2go and then use
> localhost:<your_forwarded_port> in the x2go connection dialog.

I've read about that. Problem is: I need to come up with a workable 
solution for three dozen users, many of whom are not ssh savvy, on 
three different platforms. And tweaking configuration outside of x2go 
just to connect to a different host is not practical for them, even if 
I can make it work for me.
 
> Also, x2goclient knows some debug switches to produce log files. You
> might see what's going on.

I might, if I could find said debug switches, which is what my question 
was about... Please fill me in.
 
> Third, if your bastion host is running some kind of restricted shell
> you can try to use !<hostname> instead of <hostname> (preceding the
> hostname with an exclamation mark) in the connection dialog (for
> destination or proxy or both) to disable some checks that might
> trigger your restricted shell to fail.

The jumphost allows port forwarding only, no sessions there.

Since the x2go client does offer support for an ssh proxy connection: 
How functional is it? And what is the intended setup, i.e. what is 
expected of the proxy?

Cheerio,
Hauke

-- 
     The ASCII Ribbon Campaign                    Hauke Fath
()     No HTML/RTF in email            Institut für Nachrichtentechnik
/\     No Word docs in email                     TU Darmstadt
     Respect for open standards              Ruf +49-6151-16-21344


More information about the x2go-user mailing list