Demonstration · Open-source tooling

Open-Source Certificate Verifier

A reference verifier for a post-quantum certificate. It does not just call a library’s verify(); it decodes the ML-DSA-44 signature and checks the public acceptance rules anyone can recompute, so the result is evidence rather than an assertion.

Demonstration. The result shown below is real output from running the open-source tool on an included sample certificate; it is a Sample run, not a live in-browser verification. Live in-browser verification is not wired in this build; the tool runs locally from the command line (see below).

What it verifies

For a certificate carrying an ML-DSA-44 signature, the verifier checks each of the following and holds FAIL (contradictory evidence) apart from INCONCLUSIVE (missing evidence); collapsing the two is how a verifier fails open.

  • Identity digest: the canonical subject identity hashes to the value bound in the certificate.
  • Issuer binding: the issuer public-key hash matches a trusted anchor.
  • Policy digest: the policy the certificate claims matches the one presented.
  • Validity window & revocation: current time is in range; the certificate is not revoked or replayed.
  • Signature: ML-DSA-44 signature verifies against the issuer key.
  • Rejection-sampling bounds: the signature is decoded (FIPS 204) and the public norm bound (∥z∥∞ < γ₁−β) and hint density (≤ ω) are recomputed from the bytes.

Why that matters

A verifier that only wraps verify() tells you a library returned true. This one recomputes the public acceptance rules from the signature bytes, so a reviewer can independently confirm the result. It is pure Python over a reference ML-DSA-44 implementation and touches nothing in the shipped tunnel path.

Flag This page makes no security claim beyond what the tool computes on the sample input. No certification, assurance level, or production-readiness is asserted here.

Sample verification result

Real output from release1_verify.py verify-cert cert.sample.json, run against the included sample certificate. Sample: illustrative

CheckResultDetail
Parameter setML-DSA-44matched
Identity digestPASScanonical identity hash matches
Signature verificationACCEPTreason_code: none
Signature encodingPASS2420 bytes, c_tilde|z|h decoded
Norm boundPASS∥z∥∞ = 130863, bound γ₁−β = 130994
Hint densityPASShint weight 60 of ω 80

Abbreviated tool output (JSON):

{ "parameter_set": "ML-DSA-44", "identity": { "identity_match": true }, "signature_verification": { "status": "accept", "reason_code": null }, "rejection_sampling": { "checks": [ { "check": "signature_encoding", "result": "pass", "detail": "2420 bytes, c_tilde|z|h decoded" }, { "check": "norm_bound", "result": "pass", "detail": "||z||inf = 130863, bound gamma1-beta = 130994" }, { "check": "hint_density", "result": "pass", "detail": "hint weight 60 of omega 80" } ] } }

Tool build hash and full field hashes are emitted by the tool; they are omitted here for brevity. Figures are from one run on the sample certificate.

The negative-test battery

Correct accepts are only half the story; a verifier must also reject correctly. The tool ships a negative-test battery that exercises each rejection reason (tampered subject, untrusted issuer, policy mismatch, expired, revoked, zeroed or truncated signature, violated norm bound, violated hint density, and more) and confirms each returns the right outcome. Sample

$ python release1_verify.py self-test PASS valid certificate -> pass PASS missing field -> malformed_input -> inconclusive PASS wrong parameter set -> fail PASS tampered subject -> identity_mismatch -> fail PASS untrusted issuer key -> fail PASS policy digest mismatch -> fail PASS expired / revoked certificate -> fail PASS zeroed / truncated signature -> fail/malformed PASS norm bound / hint density violated -> fail PASS no trust anchor -> inconclusive, not fail -> inconclusive ... 20/20 vectors pass (FAIL and INCONCLUSIVE held apart)

Verify a certificate

In-browser verification is an affordance only in this build. The reference tool runs locally from the command line; the control below is disabled and documents the intended flow. Live verify not wired: flagged

Verify (local CLI only)

Run it yourself with the open-source tool:

$ python release1_verify.py self-test $ python release1_verify.py verify-cert cert.sample.json $ python release1_verify.py explain-rejection cert.sample.json

The tool is pure Python over a reference ML-DSA-44 implementation. Running it requires a local Python environment with the reference PQC signature library installed.