Repository navigation
Conversation
Every SERVER testcase of x509-limbo with a DNS or IP peer name through both engines, signatures accepted on both sides. 23 of 9,791 differ, each listed with its reason. The corpus plumbing moves to tests/limbo/common.rs so both suites share it. Co-Authored-By: Claude Opus 5.5 <[email protected]>
The corpus's generated fields are only all used there, and it reports the clazel-conformance summary line xtask reads. Co-Authored-By: Claude Opus 5.5 <[email protected]>
atiernan
had a problem deploying
to
full-verification
November 5, 2026 05:06 — with 
GitHub Actions
Error
GitHub Actions
Error
Stacks this branch on #126. Its wildcard change makes webpki and us agree on webpki::san::public-suffix-private-namespace-wildcard-san, so 22 testcases differ, not 23. Co-Authored-By: Claude Opus 5.5 <[email protected]>
atiernan
requested a deployment
to
full-verification
November 5, 2026 21:19 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
This branch is waiting to be 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.
Stacked on #126 (base
phase3/wildcard-icann), which is stacked on #124: merge those first.The differential of path validation against
rustls-webpkithat 3.5b planned, one of the pieces of tier 2 evidenceclazel-x509was missing.What's here
tests/limbo/differential.rs, run bytests/conformance_limbo.rs: everySERVERtestcase of x509-limbo with a DNS or IP peer name goes throughverify_server_chainandrustls-webpki0.103.16, with the same chain, anchors, time and name.clazel-crypto/tests/chain_limbo.rs.tests/limbo/webpki_differences.rslists every difference with its reason. The test fails on an unlisted difference, a listed case that stops differing, or a change in the pinned counts.rustls-webpkiandrustls-pki-typesbecome dev-dependencies ofclazel-x509. Both were already allowlisted; no new package.Result
Of 9,791 testcases compared, 970 are accepted by both, 8,799 refused by both, and 22 differ:
rfc5280::eku::ee-without-eku, where limbo accepts, is already an expected failure).clazel-crypto's real links refuse them.No difference showed a defect in our path validation, so no code changed. The reasons come from each engine's verdict, not its documentation. The corpus is limbo's, so certificates outside it are not covered.
Not done
clazel-x509stays at tier 0. Raising it needs CI's green full verification, and I have not yet checked the rest of rule 7 for it.Verification
CARGO_BUILD_JOBS=1 cargo xtask verify --changedon Windows endedINCOMPLETE, with no check failed. Miri, Kani, Verus and proof mutations were skipped as not installed, and the status table was skipped because not all metrics were measured. CI's full verification has not run on this PR yet, and its proof jobs need afull-verificationreviewer's approval.🤖 Generated with Claude Code