Hi,
the x2go is using libssh, which _partly_ reads your openssh config files. It understands _some_ of the options, but not all.
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.
Also, x2goclient knows some debug switches to produce log files. You might see what's going on.
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.
HTH, Uli
On Wed, Jun 26, 2024 at 11:17 PM Hauke Fath <hf@spg.tu-darmstadt.de> wrote:
Hi,
I am trying to connect with the Mac x2goclient (v4.1.2.2) through a bastion host*, essentially as a version of the openssh '-J' option.
My setup in ~/.ssh/config works for ssh, but it looks like the x2go client (libssh? Where is that in the source tree?) does not look at config.
With an ssh proxy connection configured in x2go, I can see a login on the bastion host, but nothing on the target machine. And what logs x2go has are too quickly replaced by a user/passwd login screen to be readable.
How can I have the x2go client log to a file?
Cheerio, Hauke
- My uni is going to cut off direct client access from outside the perimeter soon
-- 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
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user