rpi-otp-private-key: Describe how to store an ECDSA P-256 private key #740
Conversation
This file contains hidden or 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
lurch
reviewed
Aug 20, 2025
lurch
reviewed
Aug 20, 2025
lurch
reviewed
Aug 20, 2025
The Raspberry Pi firmware cryptography service requires a valid ECDSA P-256 key instead of a plain random number. Update the usage instructions for key-provisioning to use this key type as the example.
timg236
force-pushed
the
rpi-otp-private-key-ecdsa
branch
from
4bea902 to
9058935
Compare
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.
The Raspberry Pi firmware cryptography service requires a valid ECDSA P-256 key instead of a plain random number. Update the usage instructions for key-provisioning to use this key type as the example.