Skip to content

feat(enroll): device-enrollment gate — attested boot × cryptographic quorum - #323

Merged
mdheller merged 3 commits into
mainfrom
feat/device-enroll-fusion
Aug 4, 2026
Merged

feat(enroll): device-enrollment gate — attested boot × cryptographic quorum#323
mdheller merged 3 commits into
mainfrom
feat/device-enroll-fusion

Conversation

@mdheller

@mdheller mdheller commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Stacked on #322. The payload of the whole spine: a device joins the fleet only if BOTH hold — its boot attests (measured chain vs pinned policy, dm-verity-bound) AND a validator quorum cryptographically co-signs THIS enrollment (Ed25519 over enrollment_payload_hash, which binds device + its exact measured boot). Neither half alone suffices: attested-boot-with-no-quorum is a device nobody vouched for; 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. +3 tests (15 quorumd total): enrolls with both, rejects unattested-boot, rejects quorum-bound-to-a-different-device (replay). Completes the canon Genesis binding, on-device. Not auto-merging.

…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.
…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.
@mdheller
mdheller changed the base branch from feat/quorum-ed25519-signing to main August 4, 2026 08:01
@mdheller
mdheller merged commit e396db1 into main Aug 4, 2026
6 checks passed
@mdheller
mdheller deleted the feat/device-enroll-fusion branch August 4, 2026 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant