Skip to content

Commit fed0a06

Browse files
committed
chapter2: Clarify that hashed-nodes is only a signer hint
The hashed-nodes property is not itself protected by a hash, so a loader cannot rely on it for validation. Clarify that it serves only as a hint for the signer. Signed-off-by: Simon Glass <sjg@chromium.org>
1 parent 1be2a60 commit fed0a06

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

source/chapter2-source-file-format.rst

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -483,7 +483,10 @@ value
483483

484484
hashed-nodes
485485
A list of nodes which were :index:`hashed <pair: nodes; hashed>` by the
486-
signer. Each is a string - the full path to node. A typical value might be::
486+
signer. Each is a string - the full path to node. Since this property
487+
is not itself protected by a hash, it serves only as a hint for the
488+
signer and must not be relied upon by the loader for validation
489+
purposes. A typical value might be::
487490

488491
hashed-nodes = "/", "/configurations/conf-1", "/images/kernel",
489492
"/images/kernel/hash-1", "/images/fdt-1",

0 commit comments

Comments
 (0)