feat(attest): boot-attestation + validator-quorum verifier in Rust (L0, cross-silicon) - #321
Closed
mdheller wants to merge 1 commit into
Closed
feat(attest): boot-attestation + validator-quorum verifier in Rust (L0, cross-silicon)#321mdheller wants to merge 1 commit into
mdheller wants to merge 1 commit into
Conversation
…0, cross-silicon) The verification the canon runs IN the boot path (bootProbe halts on a failed Genesis quorum, before any network) cannot be a cloud TS service — it must run on-device, on whatever silicon the device is. So the canonical verifier is pure Rust in source-os/runtime, and the same source builds for aarch64 (Apple-Silicon M2), x86_64, and riscv64 sovereign silicon — zero arch-specific code. - runtime/quorumd: verify_quorum(&QuorumProof, payload_hash) — the M-of-N validator quorum, fail-closed, CONFORMING to the authoritative QuorumProof shape (the same one the prophet-platform Python verifier PP #1370 checks; twins over one schema, not two). Rejects sub-threshold, non-validator/duplicate signers, payload-hash mismatch, kind mismatch, malformed rule. (v1 checks distinct non-trivial sigs; per-sig FIDO2/NitroKey crypto is next.) - runtime/watchdog-validator/attestation: attest_boot(&BootProofRecord, &policy) — the measured-boot verifier, fail-closed: outcome=success, every stage verdict=verified, every pinned stage present+matching, NO unpinned stage (unmeasured surface), and the rootfs stage bound to the dm-verity root (verified-immutable ↔ measured-boot become ONE evidence chain). Empty policy attests nothing (anti-theater). - 19 cargo tests (8 quorum + 11 attestation). attest-verifier.yml tests natively on x86_64 and compile-checks aarch64 + riscv64 — the "any silicon" claim is enforced, not asserted. Supersedes the TS device-enrollment path (parked, unpushed) as the verify source of truth: the cloud admission calls THIS, it does not reimplement it. Conforms to BootProofRecord + QuorumProof.
This was referenced Aug 4, 2026
mdheller
added a commit
that referenced
this pull request
Aug 4, 2026
…quorum (Rust fusion) A device joins the fleet only if BOTH hold: its boot ATTESTS (watchdog_validator::attest_boot, measured chain vs pinned policy, dm-verity-bound) AND a validator quorum CRYPTOGRAPHICALLY co-signs THIS enrollment (verify_quorum_signed over enrollment_payload_hash, which binds the device + its exact measured boot). Neither half alone suffices: an attested boot with no quorum is a device nobody vouched for; a quorum with no attestation vouches for an unmeasured box. enroll_device() fuses #321 (attest_boot) + #322 (Ed25519 quorum). quorumd now depends on watchdog-validator + sha2. Fail-closed; pure Rust, cross-silicon. The payload hash binds the vote to device+boot so a quorum can't be replayed onto another device. +3 tests (15 quorumd total): enrolls with both, rejects unattested-boot-with-valid-quorum, rejects quorum-bound-to-a-different-device. This completes the canon Genesis binding on-device.
Contributor
Author
|
Merged into main via #323 (the stack top carried all three commits: attest → Ed25519 quorum → enrollment). |
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
1 participant
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
The verification the canon runs in the boot path (
bootProbehalts on a failed Genesis quorum, before any network) can't be a cloud TypeScript service — it must run on-device, on whatever silicon the device is. So the canonical verifier is pure Rust insource-os/runtime, and the same source builds for aarch64 (Apple-Silicon M2), x86_64, and riscv64 sovereign silicon — zero arch-specific code.(This is the course-correction from the TS path: the on-device, cross-silicon verifier belongs in Rust at L0, not TS in the cloud.)
What's here
runtime/quorumd—verify_quorum(&QuorumProof, payload_hash): the M-of-N validator quorum, fail-closed, conforming to the authoritativeQuorumProofshape (the same one the prophet-platform Python verifier [PP #1370] checks — twins over one schema, not two). Rejects sub-threshold, non-validator/duplicate signers, payload-hash mismatch, kind mismatch, malformed rule. (v1 checks distinct non-trivial sigs; per-sig FIDO2/NitroKey crypto is the next step.)runtime/watchdog-validator/attestation—attest_boot(&BootProofRecord, &policy): the measured-boot verifier, fail-closed:outcome=success, every stageverdict=verified, every pinned stage present + matching, no unpinned stage (an unmeasured surface fails), and the rootfs stage bound to the dm-verity root — so verified-immutable ([PP #1367]) and measured-boot become one evidence chain. An empty policy attests nothing (anti-theater).attest-verifier.yml— tests natively on x86_64 and compile-checks aarch64 + riscv64, so "same logic, any silicon" is enforced, not asserted. (Locally proven on aarch64/M2.)Notes
cfg(target_arch), noasm!, no platform std.Touches a workflow — flagged for human review; not auto-merging.