Hi, On Do 11 Okt 2012 18:37:01 CEST wrote:
Yes, you have to explicitly specify a private key in the session settings. During the last days I have implemented ,,auto-discovery'' of SSH private keys and SSH agent authentication (X2GoClient already has this feature and also a session switch for that).
I tried setting to the private ecdsa key on the client, but it says invalid private key.
Python Paramiko (the SSH framework I use in Python X2Go does not understand ECDSA keys, yet. Only RSA and DSA. Paramiko upstream has been unmaintained for a while, but a guy from Frisco now has become the official upstream owner of the Paramiko code and development currently goes straight towards 1.8.0. So, please be patient and wait a little more for ECDSA.
The session auto-starting (and also profile auto-conecting) has to be enabled by some command line switches: pyhoca-gui --auto-connect --start-on-connect --resume-on-connect If you use those options on the cmdline, the autoconnect and autostart features in the session profile will become functional. (hmmm... maybe I should enable those by default???)
OK that works, thanks. I modified the KDE menu entry to change the default command.
Great to hear! Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: [email protected], http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgp7qs3XSz6Dn.pgp
Description: Digitale PGP-Unterschrift
_______________________________________________ X2Go-User mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-user
