On Sat, 28 Nov 2015 10:24:32 +0000 (UTC), Bill Damage wrote: > The log I see says its not using the password but the key. I have > regenerated the key but it didn't help. This setup has been fine for > years. Could there be key *types* which became invalid, or now need > special configuration, which was caused by the OpenSSL update?
Yes, DSS keys are now disabled by default, but can be re-enabled if really needed. See http://www.openssh.com/legacy.html > NX> 203 NXSSH running with pid: 3708 > NX> 285 Enabling check on switch command > NX> 285 Enabling skip of SSH config files However, if nx is ignoring your SSH config, I'm not sure how you can tell it to use > NX> 285 Setting the preferred NX options > NX> 200 Connected to address: 192.168.62.4 on port: 22 > NX> 202 Authenticating user: nx > NX> 208 Using auth method: publickey > NX> 204 Authentication failed. Where is the information from the *server* log. -- Neil Bothwick Earlier, I didn't have time to finish anything. This time I w
pgpuKTeEuoytz.pgp
Description: OpenPGP digital signature
