Regenerate public key on boot, to avoid accidental mismatch. #4916
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
thebentern
approved these changes
Sep 30, 2024
caveman99
force-pushed
the
check-keys
branch
from
82ad326 to
8d4d9c5
Compare
caveman99
approved these changes
Sep 30, 2024
|
why is STM32 failing all of a sudden on this? |
I probably goofed up the ifdef |
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.
A failure mode that we might accidentally enable is an old or bogus public key paired with a new private key. It's trivial to regenerate the public key on boot to avoid this
Download firmware-2.5.4.5cf6ffc.zip. This artifact will be available for 90 days from creation
ld or bogus public key paired with a new private key. It's trivial to regenerate the public key on boot to avoid this.