John A. Sullivan III <jsullivan@...> writes:
Hello, all. We recently recreated an X2Go Server and found we had serious ssh key issues when we tried to connect from the previously existing X2Go clients. We're still working these through so I'll list them in the order we find them.
The GUI key popping up Accept Key dialogs with Yes and No options but no text. It was only when we canceled that we saw the error message about there being an old, conflicting key. By the way, we use both hashed known_host files and non-default ssh ports. This created a problem when we went to remove the offending keys in that the syntax ssh-keygen -R <server name> did not work. We needed to use ssh-keygen -R [<server name>]:<port number> (note the brackets).
I've seen one of the symptoms you describe:
The GUI key popping up Accept Key dialogs with Yes and No options but no text. It was only when we canceled that we saw the error message about there being an old, conflicting key.
I used vi to remove the entry in my hosts file. But that blank pop up that just asks: YES NO and nothing else ?? Selecting YES didn't seem to do anything. NO at least popped up an error message in another window. <snip> You may have a second conflict. There are sometimes entries for both
On Thu, 2010-03-25 at 19:51 +0000, brian mullan wrote: the host by name and IP address. One needs to remove both to avoid any error messages (perhaps X2Go is only capturing stdout and these messages are written to stderr - just a guess - I've yet to look at the code). You can probably tell by opening a command line ssh session and seeing what message it gives you.
Let's say we have x2gohost.me.com at 1.2.3.4. one would need to do ssh-keygen -R x2gohost.me.com ssh-keygen -R 1.2.3.4
If one uses non-standard ssh ports (an excellent security idea), then the names must be in brackets with the port, e.g., ssh-keygen -R [x2gohost.me.com]:222 ssh-keygen -R [1.2.3.4]:222
At least, that's how it was for us. Hope this helps - John