[FreeNX-kNX] QtNX cannot login with custom key

[Robin Atwood]

On Thursday 25 Dec 2008, Robin Atwood wrote:
> I have just installed FreeNX 0.72, nxclient 3.2.0 and qtnx 0.9. To start
> with I used the nomachine keys and could login via both nxclient and qtnx.
> But then I decided the supplied keys were very secure and generated my own
> custom ones. I then restarted nxserver, started nxclient and imported the
> new private key and I was able tologin successfully. However, I then
> started qtnx and imported the new key and when I logged on I got:
>
> robin at opal ~ $ qtnx
> Process started
> stderr> NX> 203 NXSSH running with pid: 14936
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: 192.168.1.2 on port: 22
> stderr> NX> 202 Authenticating user: nx
> stdout> NX> 208 Using auth method: publickey
> NX> 204 Authentication failed.
> Process exited
>
> It is as if qtnx is not using the new key, but I can see the right one in
> ~/.qtnx. This is not a show-stopper since nxclient works but does anyone
> have any idea what the problem is. Searching does not reveal anything
> similar.

QtNX ships the No Machine supplied key in /usr/share/qtnx/id.key. When I 
renamed my own key to that file, qtnx started to work. I had to do the same 
thing on two machines. Go figure...

-Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------