also looking at this
feat: own runtime firmware candidates
#49
24 files
+1245
-92
| @@ -47,7 +47,26 @@ process-crash evidence is not measured physical power-loss durability. Same-user | ||
| 47 | 47 | privileged disk rollback and malicious kernel/filesystem behavior require separate |
| 48 | 48 | hardware protection and are outside this host protocol's claims. |
| 49 | 49 | |
| 50 | Installed, candidate and known-good slots, authenticated image integration and | |
| 51 | health confirmation bound to an exact image and boot/session identity remain part | |
| 52 | of #42. No receipt or healthy boolean can select firmware. Physical installation, | |
| 50 | Protected preparation now uses this metadata operation to authenticate actual | |
| 51 | image bytes before and after writing the existing signed-candidate format. The | |
| 52 | same file writer serves standalone staging. Candidate inspection requires a root | |
| 53 | pin from authenticated store readback when preparation uses the current rotated | |
| 54 | root. A candidate receipt supplies no current trust or selection authority. | |
| 55 | ||
| 56 | The original format1 database journals metadata. Candidate reservation upgrades | |
| 57 | its exact schema to format2 in a single transaction, preserving all earlier | |
| 58 | records, floors and the independently pinned store identity. The writer database | |
| 59 | stays format1. New code reads both formats; older binaries reject format2 before | |
| 60 | rewriting it. Missing/corrupt or unknown schemas are never reinitialized. | |
| 61 | ||
| 62 | Format2 adds bounded owned candidate records and one active-reservation index. | |
| 63 | A record binds the exact attempt/generation and generated signed description, | |
| 64 | is committed before image IO, and changes to prepared only after authenticated | |
| 65 | bytes and full candidate-file readback. The files use exclusive immutable-ID | |
| 66 | directories inside the private store. Explicit retirement preserves the files | |
| 67 | and history. Metadata-only recovery cannot promote a reserved candidate based on | |
| 68 | its receipt. Recorded-byte status is not current-policy authorization. | |
| 69 | ||
| 70 | Installed and known-good slot roles and health confirmation bound to an exact | |
| 71 | image and boot/session identity remain part of #42. No receipt or healthy boolean can select firmware. Physical installation, | |
| 53 | 72 | bootloader behavior, secure boot and hardware anti-rollback remain gated by #2/#9. |