Arch Linux

Description:

I got x2goclient/x2goserver working OK, but had an error related to ssh that I had to find a solution to by Googling.

Connecting via ecdsa encryption doesn't work (if I understand correctly). To fix the problem, on the server the three "HostKey" lines for protocol version 2 need to be uncommented, then sshd should be restarted. On the client, one must manually remove from ~/.ssh/known_hosts any "ecdsa-sha2-nistp256" lines for connecting to the server before connecting through x2goclient. Doing these things allows a connection to be made. (Afterwards, I have an "ssh-rsa" line in my known_hosts file and both x2go and ssh connect properly.)

Please see this thread on the x2go-user mailing list:

http://lists.berlios.de/pipermail/x2go-user/2011-October/000445.html

My feature request is to print a short message about these two problems -- assuming they affect other users, too -- or include something in a README file under /usr/share/doc

Additional info:

x2goserver 4.0.0.0-4
x2go-agent 3.5.0.17-3
x2goclient 4.0.0.3-1

Steps to reproduce:

1.) Install x2goserver and x2goclient
2.) Use ssh to connect to server, leaving an "ecdsa-sha2-nistp256" line in the ~/.ssh/known_hosts file.
3.) Connect using x2goclient. Error message: "The host key for this server was not found but an othertype of key exists.An attacker might change the default server key toconfuse your client into thinking the key does not exist."

HTH, thanks.

Clemmitt