Re: [dm-crypt] Using dm-verity+dm-crypt on rootfs (Embedded Linux)

[Milan Broz <gmazyland@gmail.com>]

On 07/08/2020 11:15, Andrii Voloshyn wrote:
> Hi there,
> 
>       Spent quite some time looking on the Internet for a reference, and couldn't find anything that would satisfy my requirements.
> Let's imagine an Embedded Linux setup, where size of the NOR flash is limited to say 16MB, root filesystem is squashfs, and assume
> that the bootloader (U-Boot) is trusted, and it validates kernel+dts. Alright, now I need to check validity of the rootfs, plus it needs to be
> encrypted, and failsafe  (in case power is gone while writing to the flash). So I guess, I need to use a combination dm-verity+dm-crypt?

You can use that, but dm-verity is read-only device (but that;s what you awant here, I guess). Then all you need is to properly store and sign dm-verity root hash.

DM-verity here provides data integrity, dm-crypt then confidentiality protection.

>      
>       From my experiments, I found out that I couldn't really use LUKS, as the header size would not fit into the flash. So I need to use plain mode, and that's Ok.

You can, LUKS2 header can be scaled down to be even smaller than LUKS1. Did you try that? Activation will be much simpler for you later.

Seems we do not have it in FAQ yet, but the idea is described here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932437#10

>       Now, the question is, what information to pass to the kernel, and how (bootargs?, initrd?), so that it could verify and mount encrypted squashfs as rootfs?
>       Have seen a lot of articles how to get it done on a partition, USB drive, etc. but not as the rootfs.
> Any reference on any project already existing or documentation would be helpful. Or, any thoughts on how it could be done differently?

I think you are reinventing what Android and ChromeOS is doing already ;-)

Milan