Agent: reset supported_private_key_algorithms for every key #1995
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I think I found a bug in the agent login.
I have ssh-agent with 3 certificates loaded. I'm able to log in to my server with a classic ssh client but not with Agent from this library. I figured out that the problem is after the first key is not accepted (if it is not accepted), in the
supported_private_key_algorithms
property are ommitedrsa-sha2-256
andrsa-sha2-512
algorithms and onlyssh-rsa
is kept. Butssh-rsa
is disabled by default in mysshd
and then the second and next keys are tried only withssh-rsa
which is declined bysshd
.I think every key from the agent should start with all algorithms in the
supported_private_key_algorithms
property. I'm not an expert in this nor in this library - I prepare a simple fix that works for me. But I suppose that the correct solution will be different :-)