Hi (especially Mike :) ),
we're currently evaluating x2go on debian squeeze (server) / ubuntu natty (client). Basic functionality works, but some of our users will need access via an intermediate ssh hop. Now if the x2go clients (I tested x2goclient and pyhoca-gui) would honour ~/.ssh/config, I could simply roll out a ProxyCommand line, but so I have to resolve to setting up the relevant tunnels manually. pyhoca claims to have some support for intermediate hops, but I was not able to use it in any understandable way. What's the recommended way to achieve this feature?
Also, pyhoca-gui was not able to accept my rsa private key and claims it's a invalid dsa key (which is correct but not helpful ;) ).
If any of this is wrongly adressed here, please point me to the correct place.
Karsten Heymann Server Administrator IP Infrastructure
Tele Columbus Gruppe Tele Columbus Kundenservice GmbH Schillerstraße 58 10627 Berlin
Telefon: 030 3388 1981 Telefax: 030 3388 9 1981 E-Mail: karsten.heymann@telecolumbus.de http://www.telecolumbus.de
Geschäftsführer: Dietmar Schickel Sitz der Gesellschaft: Ernst-Reuter-Platz 3-5, 10587 Berlin Amtsgericht Berlin-Charlottenburg HRB 130177 B
Hi Karsten (good old friend!!!),
On Do 23 Jun 2011 16:07:23 CEST Karsten Heymann wrote:
we're currently evaluating x2go on debian squeeze (server) / ubuntu natty (client). Basic functionality works, but some of our users will need access via an intermediate ssh hop. Now if the x2go clients (I tested x2goclient and pyhoca-gui) would honour ~/.ssh/config, I could simply roll out a ProxyCommand line, but so I have to resolve to setting up the relevant tunnels manually. pyhoca claims to have some support for intermediate hops, but I was not able to use it in any understandable way. What's the recommended way to achieve this feature?
x2goclient uses libssh for setting up the ssh connection. PyHoca-GUI
uses Python Paramiko for handling everything SSH'ish. Paramiko is not
able (without explicit coding) to handle SSH config files.
PyHoca-GUI can handle SSH proxying (forwarding tunnels) for SSH
connections. Please take a look at the profile manager in PyHoca-GUI
and esp a closer look at the connection settings. If this stays a
riddle, I can send you an example session profile config privately.
Also, pyhoca-gui was not able to accept my rsa private key and claims it's a invalid dsa key (which is correct but not helpful ;) ).
This might just be a misleading error message. I always use RSA keys
with PyHOca-GUI and they work fine. The error message you encountered
could mean that the SSH priv key used with PyHoca-GUI is not in the
server-side authorized_keys file. The error message should honour this
experience and I should maybe rewrite it (it's a Paramiko message that
I catch up and push to libnotify->the-screen).
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...