Agent key not being used in 12.5.1.0
I've just upgraded to v 12.5.1.0, and it seems like my SSH connections aren't using my private key loaded in via the integrated Key Agent (which is running).
Instead, I'm now getting prompted for a user account password, instead of just using my private key (which was working fine beforehand).
The remote server (Linux) only registers the password auth .method in /var/log/secure (not an invalid key, for example), but RDM logs for the key entry claim key auth was used...
Please advise.
All Comments (4)
Hello Jasper,
I've been assigned to take a look at this issue. If I find the issue or have any questions I'll update this thread.
Regards,
Hubert Mireault
Jasper,
I was able to reproduce the issue under specific circumstances. I can only reproduce it if I remove a key, then stop the agent, then start it back up again. Can you confirm you do something similar? If not, I would like to know what steps you can take to reproduce the problem. In our environment, if we start the agent a single time and load our keys (either manually or automatically), the SSH can use them properly.
Regards,
Hubert Mireault
Hiya,
It wasn't any particular odd use case, just having it running with the key in there.
Tried adding / removing / readding, start / stop the service, nothing seemed to help.
However, with the 12.5.2.0 release today, the issue appears resolved, so thank you :)
That's great news, thanks for letting us know.
Regards,
Hubert Mireault
