-
Notifications
You must be signed in to change notification settings - Fork 59
feat: use SSH host certificates #3786
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
✅ Deploy Preview for constellation-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
4a02c6b
to
b566934
Compare
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.
Mostly LGTM!
b566934
to
aaf5e88
Compare
Do these certificates work across node reboots? |
3dfbfce
to
679f67b
Compare
As long as the master key doesn't change they should, but I'll test this just to be sure |
5b73d2a
to
1950103
Compare
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.
looks good to me if tests pass
c2df904
to
58066e5
Compare
This reverts commit 9c69f954a5efb00e8c95835d98a4c2e6b87c984c.
4e3f6d4
to
8b17992
Compare
Coverage report
|
Context
Currently, if you use the emergency SSH access, you have to manually validate each nodes host key (TOFU). This PR fixes that by introducing host certificates.
Proposed change(s)
Additional info
Checklist