Repository navigation
Conversation
RFC 5280 §4.2.1.10: either permittedSubtrees or excludedSubtrees MUST be present; X.509 §9.4.2.2: at least one shall be present. The spec now refuses the empty SEQUENCE in parse_name_constraints_fields, as policy_constraints already does for its own. A new mutation is certified by lemma_empty_name_constraints_are_rejected; the trailing-bytes mutation's witness moves to a non-empty value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The exec decoder follows the spec. The independent transcription's equivalence no longer excludes the empty value (both now refuse it), the unit test flips, and limbo's both-null case is now refused because the intermediate does not decode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
basicConstraints' criticality (path/spec.rs: two NSS roots are non-critical; Chrome and webpki do not read it), policyConstraints on the target (path/profile.rs: RFC 5280 §6.1.5 (b) processes it), and X.501 §9.3's distinct types within an RDN (name/spec.rs: RFC 5280 does not ask it). Comments only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pec) RFC 5280 §4.1.2.6: if the subject is an empty sequence, the subjectAltName extension MUST be critical. A new (R) step 4 in profile::leaf_profile refuses the target as PathError::Leaf, as Chrome does (BoringSSL ParsedCertificate::Create). lemma_leaf_empty_subject gives both directions; two mutations are certified by it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…xec, tests) path::exec::leaf_profile follows the spec's step 4. x509-limbo's rfc5280::san::noncritical-with-empty-subject now agrees (65 expected failures, from 66) and becomes a rustls-webpki difference (LEAF). equivalence_requirements.rs records subject_rule as enforced on the target, not yet proven against the predicate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…equivalence One more limbo certificate's nameConstraints does not decode (the empty-NameConstraints intermediate), and one case leaves "accepted by both" in the webpki differential (the empty-subject target). lemma_p15_equivalence ran out of rlimit with the profile's new definitions in the crate; it needs none of them, and verifies in its own prover context. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Written from RFC 5280, 3279, 4055, 5480, 8410, 8017 §3.1, 7748 §5 and 8032 §5 without reading src/spki/. Its header lists what the author read and every modelling choice. 13 compute_only examples, including a real RSA-2048 and P-256 key and RFC 8410 §4's Ed25519 example. No equivalence proof covers it yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
theorem_spki_classification_fwd/back: on RSA and uncompressed P-256 and P-384 keys, spki/spec.rs and independent/spki.rs classify the same keys, with the same RSAPublicKey octets and integer values or the same point. The header lists where they differ (keys the crate leaves Unsupported, RFC 8017 validity checks) and why. Statements by one author, proofs by another; neither wrote the transcription. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ippy) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
atiernan
had a problem deploying
to
full-verification
November 20, 2026 04:48 — with
GitHub Actions
Error
The claim stands only if CI's full verification on this pull request is green; until then it is unproven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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.
Closes the remaining gaps between
clazel-x509and Tier 2. The last commit (ae7505a) raisestierto 2. That claim holds only once CI's full verification on this PR is green; the PR must not merge before then.What changed
name-constraints-one-field-present-at-decode.profile-leaf-empty-subject-needs-critical-san,-reads-criticality. Example:lemma_leaf_empty_subject.independent/spki.rs, 13compute_onlyexamples). Its author never readsrc/spki/.independent/equivalence_spki.rs). I wrote the theorem statements; a different author wrote the proofs. They show the crate's key classification agrees with the transcription in both directions, for every key the crate classifies.Unsupported, and the RFC 8017 validity checks the crate does not make.#[verifier::spinoff_prover]added onlemma_p15_equivalence.Known gaps
subject_rulein the transcription is not yet proven to match the new empty-subject enforcement inpath/profile.rs.docs/phases/phase-3.mdstill quotes the old limbo counts (9,736/66). The new counts are 9,737/65.Local verification
cargo xtask checkpassed.cargo xtask verify --changedended in FAILED, for two reasons:indexing_slicinginpath/exec.rs: fixed in 1906c9d. Clippy is clean afterwards, the focused Verus run onleaf_profileverifies, and all 22 x509 test binaries pass.clazel-tls:lemma_retry_accepted(transcription_equivalence/client.rs) andlemma_hello_alert(driver.rs). The clazel-crypto steps after them were reported failed too.clazel-tlsdepends only onvstdand is unchanged frommain, whose CI is green. These look specific to this machine (macOS), but that is not confirmed.The rest of that run passed:
I did not rerun the whole
verify --changedafter the clippy fix.CI's full verification has not run yet. The proof jobs need approval from a
full-verificationreviewer.🤖 Generated with Claude Code