Allow generating ECDSA roots and intermediates#518
Merged
Conversation
jsha
approved these changes
Oct 3, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add a new "keyAlgorithm" entry to Pebble's config, which can take the value "rsa" or "ecdsa". Leaving it unset or setting it to "rsa" preserves the same behavior as today, in which Pebble uses RSA 2048 to generate all of its root and intermediate keys and certificates. Setting it to "ecdsa" causes Pebble to use ECDSA P-256 for all of its root and intermediate keys and certificates.
This paves the way for having pebble support other not-approved-by-the-BRs key algorithms, such as ML-DSA.