-
-
Notifications
You must be signed in to change notification settings - Fork 866
Restrict algorithms for host key exchange #9214
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, I rebased your branch onto master
. One of the PR checks was failing, seemingly due to a change in goimport
's behaviour.
I can't access the logs of that failure. But in line with your comment before, I assume it's unrelated to my change. |
Currently, "ssh-rsa" is offered as host key algorithm by TSA for worker registration on port 2222. This seems to be flagged at least by some security scanners as "using deprecated SHA1 cryptographic settings to communicate." This can be verified with: nmap -Pn --script ssh2-enum-algos -sV -p 2222 tsa.example.com And results in: | server_host_key_algorithms: (3) | rsa-sha2-256 | rsa-sha2-512 | ssh-rsa This can be addressed by specifying the allowed host key algorithms on the server side as outlined here: golang/go#52132 Signed-off-by: Robert Neumayer <robert.neumayer@proton.me>
Signed-off-by: Robert Neumayer <robert.neumayer@proton.me>
You are correct. There's been a single test in that test suite that's been flaking in CI when there's high CPU usage. Re-running it. Edit: Yup, it's green now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! Just going to let the integration tests go green and then I'll merge. Thanks again for the PR 🙏
@neumayer I added you to the |
Currently, "ssh-rsa" is offered as host key algorithm by TSA for worker registration on port 2222. This seems to be flagged at least by some security scanners as "using deprecated SHA1 cryptographic settings to communicate."
This can be verified with:
nmap -Pn --script ssh2-enum-algos -sV -p 2222 tsa.example.com
And results in:
| server_host_key_algorithms: (3)
| rsa-sha2-256
| rsa-sha2-512
| ssh-rsa
This can be addressed by specifying the allowed host key algorithms on the server side as outlined here:
golang/go#52132
Changes proposed by this PR
closes #9212