Helpers to convert EC2 keys to/from SEC1 octet strings #121
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
daviddrysdale
approved these changes
Dec 18, 2025
AndrewScull
force-pushed
the
sec1
branch
2 times, most recently
from
6f6c90d to
81a9bc3
Compare
Add helper functions to build a CoseKey from a SEC1 octet string and to encode an EC2 CoseKey to a SEC1 octet string.
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 helper functions to build a CoseKey from a SEC1 octet string and to encode an EC2 CoseKey to a SEC1 octet string.
EC2 CoseKeys are defined in terms of SEC1 encodings which makes the conversion fairly straightforward and the SEC1/X9.62 format for a public key is a common interchange format so it makes loading a CoseKey to and from a crypto library an easier task (bssl-crypto, for example).