From ea2b3864dda2052e74857e4229a057facad616ad Mon Sep 17 00:00:00 2001 From: Entrpi Date: Wed, 28 Oct 2026 01:24:22 +1100 Subject: [PATCH] docs(artifacts): record which ESP metadata comparison ignores Segments are compared by their declaration. The image's and the signature blocks' format_metadata are not: every field comes from their own bytes, which content comparison already covers, and a block's image_digest_matches follows the image's content. --- docs/esp-image.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/esp-image.md b/docs/esp-image.md index 58fb257fbe..7a55a85e65 100644 --- a/docs/esp-image.md +++ b/docs/esp-image.md @@ -145,7 +145,10 @@ Artifact comparison uses each segment's `load_addr` and `data_len` as its declaration, so a segment that moves with unchanged bytes is `changed` in `metadata`. Segments pair by index: inserting or removing one shifts the paths of the segments after it. Header offsets and `classification` are not -compared; the image's own change covers the header and chip. +compared; the image's own change covers the header and chip. The image's and +the signature blocks' `format_metadata` carry no declaration: their fields +come from their own bytes, which content comparison covers, and a block's +`image_digest_matches` follows the image's content. ## Secure Boot v2 signatures