Support singing via Certificate PrivateKey - #257
Merged
Conversation
Lukasa
reviewed
Jun 24, 2025
bauer-andreas
force-pushed
the
signing-support
branch
from
June 30, 2025 15:22
1245ad1 to
c530747
Compare
Lukasa
approved these changes
Jul 1, 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.
This PR introduces two key changes to improve flexibility when working with signatures in swift-certificates. Previously, it was only possible to verify signatures using
Certificate.PrivateKey, but not to generate them.sign(bytes:signatureAlgorithm:)method onCertificate.PrivateKeyis now public, allowing users to generate signatures directly.Certificate.Signaturegains a newrawRepresentationproperty that exposes the raw byte representation of a signature.