Re: [PATCH v4 0/3] boot: fit: authenticate the dm-verity roothash
Tom Rini <[email protected]>
| Newsgroups | gmane.comp.boot-loaders.u-boot |
|---|---|
| Message-ID | <178639520566.1450255.17476771130005296710.b4-ty__47248.9259949484$1786395229$gmane$org@konsulko.com> |
On Tue, 28 Jul 2026 23:09:30 +0100, Daniel Golle wrote:
> A signed FIT configuration can delegate the integrity of a (potentially
> large) root filesystem image to the kernel's dm-verity instead of having
> U-Boot hash the whole payload at boot: the FIT carries a "dm-verity"
> subnode with the roothash, salt and block parameters, U-Boot passes the
> roothash to Linux through the dm-mod.create bootargs, and dm-verity then
> validates the filesystem block by block against it.
>
> [...]
Applied to u-boot/main, thanks!
[1/3] boot: fit: factor out node-path collection in fit_config_add_hash()
commit: ba9ce23d21e3536b7de5e5722f20b8d6be695d3c
[2/3] boot: fit: cover the dm-verity roothash with the config signature
commit: 2601d94691c00e0a05dc61241bb91d680519d49b
[3/3] test: fit: verify dm-verity roothash is covered by the config signature
commit: fe9877c7d9dea740985edd11f7ff583e311568be
--
Tom