-
Notifications
You must be signed in to change notification settings - Fork 2k
ssh: fix server to accept rsa-sha2-256 and rsa-sha2-512 signatures #187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh: fix server to accept rsa-sha2-256 and rsa-sha2-512 signatures #187
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@googlebot I fixed it. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
… public key algorithm name and signature format in user auth messages
e0490ae
to
ab4f6d8
Compare
@googlebot I fixed it. |
This PR (HEAD: ab4f6d8) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/crypto/+/325089 to see it. Tip: You can toggle comments from me using the |
…thm name with rsa-sha2-* signatures
ab4f6d8
to
ded2006
Compare
This PR (HEAD: ded2006) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/crypto/+/325089 to see it. Tip: You can toggle comments from me using the |
I noticed the unit test had a bug: incorrect public key algorithm name was used woth rsa-sha2-* signatures. Fixed it. |
@samiponkanen as I understand, the server would still not advertise support for SHA2 during KEX with your PR. Is that the case? Lines 338 to 340 in 0c34fe9
|
You are correct, this PR does not add support for sending the server-sig-algs extension. |
This pull request fixes serverAuthenticate() to accept "rsa-sha2-256" and "rsa-sha2-512" public key algorithm names and signature format in user auth messages. Additionally this pr adds unit tests for RSA publickey authentication using rsa-sha2-256 and rsa-sha2-512 signatures.
Fixes golang/go#46569