The partition probe fails closed on every path (R-1093 review, unreleased)
PART_ENTRY_* comes from the parent's table, so it proves nothing about a partition's contents unless blkid also completed: lsblk's PTTYPE is now set aside only on a blkid exit 0 (exit 2, an I/O error or a missing binary keep "device has a partition table"). An lsblk that exits 0 with output that does not parse into a device, or lists none, leaves the device unprobed instead of blank (a hole that predates R-1093). Six more TestInspect_R1093_PartitionVerdicts rows, each red-proved.
This commit is contained in:
1 parent
8561dc8a5c
commit
0963bae3c3
3 files changed
+60
-20
No files matched your search
@@ -11,6 +11,12 @@ Committed, not released — the release and its vouch are the operator's.
|
||||
that differs keeps the old, safe reading. **No new command, no sudoers or config-bundle change** (the two probes are
|
||||
the same allow-listed argv). Test `TestInspect_R1093_PartitionVerdicts` (8 rows), red-proved: with the old
|
||||
`if pttype != ""` both empty-partition rows fail `DataBearing=true reason="device has a partition table"`.
|
||||
**Hardened after the same night's review (fail-closed on every path):** `PART_ENTRY_*` is read from the PARENT's
|
||||
table, so lsblk's PTTYPE is set aside only when blkid also **exited 0** — exit 2, an I/O error or a missing binary
|
||||
keep „device has a partition table"; and an `lsblk` that exits 0 with output that does not parse into a device (or
|
||||
lists none) now leaves the device UNPROBED („could not be reliably inspected") instead of „blank" — that hole
|
||||
predates R-1093. Six more rows in the same test, each red-proved (`blkidErr` check removed → „device is blank";
|
||||
`&& parsed` removed → `Probed=true … „device is blank"`).
|
||||
- **R-978 — an abandoned second escrow ceremony no longer makes the customer's recovery code useless.** The root
|
||||
ceremony (the FELHOM_ESCROW argv, unchanged: `--upload --output=json`) used to upload the new package before the new
|
||||
code was claimed, and the hub overwrites the current package when the sealed secrets are unchanged — so a customer
|
||||
|
||||
Reference in new issue
Block a user