freenx-team team mailing list archive

[Olivier Dierick <o.dierick@xxxxxxxxxxxxxx>]

I confirm this bug was present in Gutsy and Hardy and is still present
in Jaunty for me. My preferred walkaround is to make a symbolic link
'authorized_keys' in /var/lib/nxserver/home/.ssh along with the existing
'authorized_keys2' link so that freenx still find it by its old name if
it needs it for whatever reason.

-- 
non default authorized_keys2 prevents login
https://bugs.launchpad.net/bugs/338871
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.

Status in FreeNX open source NX Server: New

Bug description:
On my up-to-date jaunty system, the authorized ssh keys reside in the file "authorized_keys", while freenx provides a "authorized_keys2" file.
This prevents client logins, as no ssh keys are found.

Renaming the file to "authorized_keys" resolves the problem.