How to fix broken NX user authentication after OpenSSL fix

It looks like OpenSSH Keys generated on Debian derived distros (Ubuntu/Voyage etc.) are REALLY bad. I’m currently rolling out OpenSSL key updates as adviced on

One casualty of this update was my NX server using freenx. It just tells me that I can’t be authenticated. In the log /var/log/freenx.log it shows the following:

— NX SERVER START: -c /usr/lib/nx/nxserver – ORIG_COMMAND=
HELLO NXSERVER – Version 2.1.0-71 OS (GPL)
NX> 105 hello NXCLIENT – Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 login
NX> 101 User: shuerlimann
NX> 102 Password:
NX> 404 ERROR: wrong password or login
NX> 999 Bye

This post talks about the NoMachine NX Server, but gave me the necessary clues:

The magic command for freenx from
on Ubuntu is

sudo rm /var/lib/nxserver/home/.ssh/known_hosts

This is necessary, as the SSH host key has been updated… Well, a more informative error message would’ve been nice, but I’m thankfull to the guys who produce freenx, anyway;-)


Latest plan: Release 2 Kubuntu 8.04 CD’s: KDE 3.5 and KDE 4.0

According to this comment by Jucato Kubuntu 8.04 will be released in two variants: one with KDE 3.5 as default, the other with 4.0.

the plan is to release 2 Kubuntu 8.04 CD´s: one with KDE 3.5.8 (or .9) as default, and one with KDE 4 as default (but of course with some KDE 3 apps)