This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
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.
📢 Type of change
📜 Description
Use a custom, relatively modern sshj config that:
💡 Motivation and Context
I decided to get this merged now rather than wait for #807 because I noticed that the default sshj config relies on an RNG that has some known weaknesses that allow its output to be distinguished from a fully random distribution (which doesn't sound too relevant in the context of SSH authentication,but should certainly be prevented by switching to a different RNG).
💚 How did you test it?
I verified that ssh-rsa and ssh-ed25519 keys still work.
📝 Checklist
🔮 Next steps
Figure out how/whether to update the changelog now or after #807 lands, which adds support for the very common
rsa-sha2-*
types.📸 Screenshots / GIFs