COSE: Add fully specified algorithm identifiers#384
Merged
JesusMcCloud merged 3 commits intoDec 9, 2025
Conversation
JesusMcCloud
approved these changes
Dec 4, 2025
JesusMcCloud
left a comment
JesusMcCloud
left a comment
Collaborator
There was a problem hiding this comment.
Mappings check out according to RFC
JesusMcCloud
had a problem deploying
to
github-pages
December 5, 2025 15:14 — with 
GitHub Actions
Failure
GitHub Actions
Failure
iaik-jheher
approved these changes
Dec 9, 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
3 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.
First step for supporting RFC 9864
Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE): Being able to parse such identifiers, e.g. when coming from Multipaz ISO proximity verifier app to Valera.
/cc @tlenz