SSH key agent not working version 2025.2.11.0

Hello,

We are working to reproduce the issue but to make things faster we would need some logs.
If you have a terminal session that you could enable the logging and set the verbose level to 2 and send it to us, it would help us greatly

Best regards,

Hello,

I did create a log, and find the issue in it.
After the line: Received userauth failure there was a line with too many attempts.
That was the reason.
There were too many attempts, (I had a lot of keys into the SSH key agent).
After I removed all keys and insert the ones I need again, all start working again.
Perhaps there is some limit for the attempts set, which cause this error.
Anyhow, it is solved for me now.
Thanks in advanced.

Kind regards,
Ruben van Milaan.

This is still an issue.

I f you uses more then 6 keys, it is not possible to use the SSH Key Agent:

[9/1/2025 1:51:05 PM] Agent has 17 keys
[9/1/2025 1:51:05 PM] Sending userauth init request
[9/1/2025 1:51:05 PM] Received userauth failure: publickey,gssapi-keyex,gssapi-with-mic
[9/1/2025 1:51:05 PM] Starting authentication by key
[9/1/2025 1:51:05 PM] Validating public key: rsa-sha2-512
[9/1/2025 1:51:05 PM] Received userauth failure: publickey,gssapi-keyex,gssapi-with-mic
[9/1/2025 1:51:05 PM] Validating public key: rsa-sha2-512
[9/1/2025 1:51:05 PM] Received userauth failure: publickey,gssapi-keyex,gssapi-with-mic
[9/1/2025 1:51:05 PM] Validating public key: rsa-sha2-512
[9/1/2025 1:51:05 PM] Received userauth failure: publickey,gssapi-keyex,gssapi-with-mic
[9/1/2025 1:51:05 PM] Validating public key: rsa-sha2-512
[9/1/2025 1:51:05 PM] Received userauth failure: publickey,gssapi-keyex,gssapi-with-mic
[9/1/2025 1:51:05 PM] Validating public key: rsa-sha2-512
[9/1/2025 1:51:06 PM] Received userauth failure: publickey,gssapi-keyex,gssapi-with-mic
[9/1/2025 1:51:06 PM] Validating public key: rsa-sha2-512
[9/1/2025 1:51:06 PM] Received disconnection message, code: 2
[9/1/2025 1:51:06 PM] Reason: Too many authentication failures
[9/1/2025 1:51:06 PM] Disconnection in progress
[9/1/2025 1:51:06 PM] Bytes sent: 3824, Bytes received: 2049
[9/1/2025 1:51:06 PM] Packets sent: 11, Packets received: 12
[9/1/2025 1:51:06 PM] Kex completed: 1
[9/1/2025 1:51:06 PM] Disconnecting

As you can see I haven at the moment 17 keys, and still counting.
But if I start a session, it tries 6 different keys and stops.
I'm 100% sure the right key is in the key agent.
Maybe we can add an extra option for the key agent, count the keys (see logfile first line!) and try the amount of keys?
I hope this will be fixed soon.

Kind regards,
Ruben van Milaan

Hello,

We are going to look into it.
Just to be sure, can you confirm if the server doesn't have a limit of try?
Initially when a talked about the issue to the developper taking care of the ssh key agent, he did say that on the RDM side there's not really a limit to how much keys you can circle through,
the limit being usually set by the number of try the server is willing to accept.
Still we are going to test on our side.

So just to get the parameters right:
-Authentication vis SSH Key agent
-more than 6 keys.

Is everything right?
Best regards,

Hi Michel,

Thanks for the follow up.
I can confirm that this is the case.
I checked also the SSH configs and we don't use a MaxAuthTries, so it is by default 10, but we have disabled this by default.

Kind regards,
Ruben van Milaan