sorted by: recent | see : popular

Content Tagged with System + Security

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 http://wiki.debian.org/SSLkeys.

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 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
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: http://lists.kde.org/?l=freenx-knx&m=116542288527396&w=2

The magic command for freenx from http://datakeylive.com
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