Thank you for your answer. We use https://code.x2go.org/releases/binary-win32/x2goclient/releases/4.1.1.1-2018... and not python GUI, as this implementation is very old (from 2015) and in my test, it didn't work well and was less convenient (than x2goclient).
On 19/03/2018 13:09, Mike Gabriel wrote:
Hi,
On Di 13 Mär 2018 13:26:16 CET, Antoine Tran wrote:
Dear all,
Regarding https://wiki.x2go.org/doku.php/doc:howto:ssh-agent-workaround, what is the current status? I tried latest 4.1.1.1 and this issue is still not solved, even though there might be some improvement. I can see now in export what seems to me a valid PID, socket, etc.:
> export
declare -x SSH_AGENT_PID="16945" declare -x SSH_AUTH_SOCK="/tmp/ssh-CAjx51laLmty/agent.16903" declare -x SSH_CLIENT="10.0.1.81 33414 22" declare -x SSH_CONNECTION="10.0.1.81 33414 172.17.0.2 22"
> ps aufx|grep 16945 trana 16945 0.0 0.0 52916 584 ? Ss 12:16 0:00 \_ /usr/bin/ssh-agent /bin/bash -c exec -l "/bin/bash" -c "/usr/bin/env LD_LIBRARY_PATH=/usr/lib64/nx/X11/Xinerama:/usr/lib64/nx/X11 startkde"
> ll $SSH_AUTH_SOCK srw------- 1 trana trana 0 Mar 13 12:16 /tmp/ssh-CAjx51laLmty/agent.16903
But the ssh from a a console in Kde, that has these variable, does not use ssh agent. I can see that in ssh -vvvvvvvv
Thanks.
still not being worked on afaik.
PyHoca-GUI / Python X2Go has ssh-agent forwarding for ages. However, with recent Debian / Ubuntu, I see various breakages regarding the newly uploaded Paramiko version (SSH client implementation in Python utilitzed by Python X2Go).
I need to take some time and get PyHoca-GUI and -CLI up to speed (Python 3, bug fixes, etc.).
Mike
-- My THALES email is antoine.tran@thales-services.fr. +33 (0)5 62 88 84 40 Thales Services, Toulouse, France