summaryrefslogtreecommitdiff
path: root/contrib/examples/httpd/https_example
diff options
context:
space:
mode:
authorDaniel Golle <[email protected]>2026-05-16 00:38:07 +0100
committerTom Rini <[email protected]>2026-05-27 13:41:33 -0600
commit1e4829855234d8dc91c2840a79e9a64a2e8bf3a6 (patch)
treed1bdd6510852aebcbfc48b293567e165c916fc8c /contrib/examples/httpd/https_example
parent96e180d354de563ce6dc68cbcac26d67f326940d (diff)
tools: mkimage: add dm-verity Merkle-tree generation
When mkimage encounters a dm-verity subnode inside a component image node it now automatically invokes veritysetup(8) with --no-superblock to generate the Merkle hash tree, screen-scrapes the Root hash and Salt from the tool output, and writes the computed properties back into the FIT blob. The user only needs to specify algorithm, data-block-size, and hash-block-size in the ITS; mkimage fills in digest, salt, num-data-blocks, and hash-start-block. Because --no-superblock is used, hash-start-block equals num-data-blocks with no off-by-one. The image data property is replaced with the expanded content (original data followed directly by the hash tree) so that subsequent hash and signature subnodes operate on the complete image. fit_image_add_verification_data() is restructured into two passes: dm-verity first (may grow data), then hashes and signatures. Signed-off-by: Daniel Golle <[email protected]> Reviewed-by: Simon Glass <[email protected]>
Diffstat (limited to 'contrib/examples/httpd/https_example')
0 files changed, 0 insertions, 0 deletions