| Subject: | x2go and ssh-agent forwarding |
|---|---|
| Date: | Thu, 19 Oct 2023 21:21:48 +0100 |
| From: | graeme vetterlein <graeme@vetterlein.com> |
| To: | x2go-user@lists.x2go.org |
Anybody know if this is still current?
https://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround
It suggests a patch was available in 2017
I can see a fresh ssh-agent(1) is getting started (so blocking access to the original client one)
also I note the use of -oClearAllForwardings on the
ssh call x2go makes ..... neither look like good news :-(
I did try (XFCE) :
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n
-t bool -s false
xfconf-query -c xfce4-session -p /startup/ssh-agent/type -n -t
string -s ssh-agent
And indeed the ssh-agnet was not started, but SSH_AUTH_SOCK
(to tmp/ssh-xxxxxx/agent.PID [ literally PID not a number ]
FYI I need to use the keys to access github and I don't want to
put them on the machine I'm x2going into.
BTW. I also ran a test using a "custom desktop" of /usr/bin/lxterminal ...and in that terminal SSH_AUTH_SOCK was set
to a non-existant filename(socket) in ~/.x2go
--
Graeme