Hi List,

subject says it all, so here's a short description of the test environment:

Server is a vserver running Debian Lenny (oldstable/5.0.9) but the 2.6.32-5-vserver-amd64 kernel (as the host is Debian Squeeze). dpkg -l|grep x2go ii nxcompshad
3.4.0-1-1 nx based library needed by the x2go system ii x2go-keyring
2011.04.19+lenny~main~10~build1 GnuPG keys of X2go developers ii x2goagent
3.4.0-3-1 Special NX-ized client, was developed by NoMachine to handle X ii x2goserver
3.0.99.8-0~x2go-bpo1+lenny~main~388~build1 X2go server daemon scripts ii x2goserver-extensions
3.0.99.8-0~x2go-bpo1+lenny~main~388~build1 X2go server daemon scripts (extensions)

Client is "Windows 7 Home Premium", 32-Bit, running X2Go Client V.3.99.0.1 (Qt-4.5.3) - not a clean install, but installed over a previous, older version.

1. Accidentally attempting to connect to the wrong server crashes the client. What happened:

• Host is configured to use private key files and doesn't have a corresponding user
• Vserver is running sshd on a different IP/port
• Client connects to the host instead of the vserver due to the wrong port number, using password-interactive authentication, which is denied by the server, also, there is no user present on the host that matches the given username ==>Crash (System message offering to close the program or look online for help)

2. Attempting to connect to a host that has a different ssh key than the one seen previously shows a small popup "Authentication failed" that complains about the offending key, but it immediately causes a Crash (same as above) - there's not even a chance to click on the "OK" button of that popup.

Both cases should be handled more gracefully.

Kind Regards, Stefan