Repository navigation
clazel-x509: X.509 decoders and name matching (3.5b, partial), tier 0 - #14
Merged
Merged
Conversation
This was referenced Oct 26, 2026
atiernan
marked this pull request as ready for review
October 27, 2026 11:04
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The views of SubjectPublicKeyInfo, PublicKey and RsaPublicKey map pub fields one to one; closing them stopped other crates from relating a parsed key's fields to `parse_subject_public_key_info`'s spec, which clazel-crypto's signature verifier needs. No semantics change; whole- crate Verus passes with 0 errors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Third of the stacked PRs that replace #1 (TLS takeover plan, step 1). It stacks on #10 because x509 depends on
clazel-der. This addscrates/clazel-x509byte for byte as it is on the TLS stack (I checked: no difference fromphase3/tls-bootstrap-ccs), plus itsCargo.lockentry. It has no third-party dev-dependencies and no generated test data, so it needs no allowlist rows and no xtask changes.What it is: decoders for the envelope, TBS, extensions, time, SPKI and name constraints, partial leaf checks, and RFC 9525 host matching. It has no path building or validation and no trust anchors yet.
Local results:
cargo xtask checkreported STATIC CHECKS PASSED.cargo fmt --all --checkand strict clippy are clean, andcargo test -p clazel-x509passes. I did not run Verus, mutations or a full verify locally. The crate stays attier = 0.Needs Alex's OK to merge, after #10.
🤖 Generated with Claude Code