Support RFC 9360 - X509 fields parsing in protected headers#10
Merged
mingweishih merged 1 commit intoAzure:mainfrom Apr 17, 2026
Merged
Support RFC 9360 - X509 fields parsing in protected headers#10mingweishih merged 1 commit intoAzure:mainfrom
mingweishih merged 1 commit intoAzure:mainfrom
Conversation
Signed-off-by: Ming-Wei Shih <mishih@microsoft.com>
radhikaj
approved these changes
Apr 17, 2026
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.
Description
This PR implements RFC 9360, which supports X509 fields parsing in protected headers in signed CoRIM.
Related Issues
Checklist
cargo test --allpassescargo fmt --all -- --checkpassescargo clippy --all -- -D warningspasses