Repository navigation
security: upgrade P-256 crypto and preserve identity encodings - #10
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
Summary
Upgrade p256 to 0.14 and enforce crypto-bigint >=0.7.6 for RUSTSEC-2026-0387. Use fallible OS key generation and the new SEC1 encoding API. This changes no protocol semantics on main.
Public-only fixtures generated with the unmodified 0.3.0 SDK verify existing PEM/JWK keys, key IDs, DER JWT signatures, and saved TOFU pins. Rust callers that name public key types must use p256 0.14 too.
Verification
A separate 0.3.1 maintenance backport preserves the released wire protocol for AgentSniff; this PR does not publish main's unreleased protocol changes.