static keys from hetzner rescue systems and tarballs #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Anything related to #4 included? |
|
No, I checked that. It seems they have removed all images that contained those keys. |
BenBE
approved these changes
Aug 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These are various keys in hetzner install images and rescue system images that are or were accessible by booting the hetzner rescue system.
I looked into this and none of them look particularly serious, it seems their current installation routine replaces the keys, but some legacy systems may still have host keys that can be found here. Also some older install images seem to have installed example certs that at least in one case I could tie to a valid (but expired) TLS certificate. So nothing particularly interesting, but good to keep them for auditing purposes.