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