I wonder if authorized.crt file allows to place restrictions for IP, command etc. like the ones which can be added at the beginning of the line of each pulic key in /root/.ssh/authorized_keys. Hope this naive explanation helps someone like me who is not on the professional side. In NX client under WIN select Session – Edit – Advanced – Private key – Settings file field: browse for private key file in SSH format, not the file saved by PuTTYgen. crt format used to input certificates in browsers and mail clients should not be used:Ģ. SSH seems to have some setup allowing it to generate the pulic key in this format, but I am not sure about the syntax. The. This is the output of PuTTYgen generate window (not the saved file) and is different from SSH / XCA format of the generated public key. nx/config have 0700 permissions, authorized.crt has 0600 permissions, owner root) should be the same format as in /root/.ssh/authorized_keys: Public key in /root/.nx/config/authorized.crt (.nx and. I solved the problem after some head banging. WARNING! Process ‘/usr/NX/bin/nxexec –cat –user root –path config/authorized.crt’ with pid ‘18560/18560’ finished with exit code 1 after 0,17 seconds. Switched debugging into level 7 but the log is growing like a mushroom and I find no clue in this mess. NX> 500 ERROR: Public key authentication failed NX> 500 WARNING: NX server was unable to login as user: loene NX> 500 WARNING: Please check. PuTTY and WinSCP authenticate OK with key pair generated by PuTTYgen.exe and public key in /root/.ssh/authorized_keysĪcceptedAuthenticationMethods is ALL (default) Tried to edit public key in one line as recommended for PuTTY – same result. Tried generating keys 1024bit with PuTTYgen.exe, with nxkeygen (2048bit), with XCA (2048bit). In Edit connection – Advanced – Private key – Settings I input private key file. nx and config have 0700 owner root) and authorized.crt (0600 owner root). was strictly followed: I added /root/.nx/config folder (both. But when I try to connect via NX protocol with private key I get the error : The session negotiation failed. All works fine when I use user & password with NX protocol for system login authentication (as root). Distribute the secret key /usr/NX/share/keys/ to clients and import it in the client GUI (Configure General. NX> 700 WARNING: nxsetup cannot validate the sanity of the current installation: NX> 700 WARNING: the current system or NX configuration could be broken. I only started on a new PKGBUILD for the 4.0.x line a few minutes ago, but Ive got to get to my work work so itll have to wait a little. It seems that theyve renamed the product from NoMachine NX to just NoMachine, so it seems more appropriate to call the package nomachine now. I’m connecting to NoMachine free server 5.0.63 for Fedora23 from Windows 10 same version. NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed. That said, the 'nx-all' package might become 'nomachine' soon.
0 Comments
Leave a Reply. |