Closed sergioprado closed 9 months ago
LGTM. Just have some questions to help me understand some points here. So for someone building the Toradex BSP reference image. They would want to inherit
tdxref-signed.bbclass
in their build, correct?
Exactly.
In which case, is the goal to make this bbclass become the BSP reference equivalent for the
torizon-signed.bbclass
that is inmeta-toradex-torizon
? Or will it's purpose differ a bit?
Yeah, the idea is to have just two major classes: tdxref-signed.bbclass
for BSP users and torizon-signed.bbclass
for Torizon users.
Also, and I might be jumping ahead. I assume it wouldn't make too much sense to inherit
torizon-signed
andtdxref-signed
in the same build, right? Would there be any issues if someone inadvertently did that?
It doesn't make sense to inherit both, and it will probably not work, since they will use different technologies for rootfs authenticity check (dm-verity for BSP and composefs for Torizon).
Okay, perfect thanks for clarifying my understanding here. Well I have no more points to raise. @rborn-tx Did you want to take a look here as well?
@jsrc27
Did you want to take a look here as well?
Absolutely. I didn't have time yet but I intend to do it before the weekend.
The implementation so far looks good to me. Since it's been approved already, let me go ahead and merge it.
This class is responsible for creating a verified BSP reference image with full chain-of-trust support.
It inherits
tdx-signed
to sign boot artifacts (bootloader and FIT image) andtdx-signed-dmverity
to boot a signed rootfs image with dm-verity.The
tdx-signed-dmverity.class
implementation is currently incomplete, and for now it just builds and boots the rootfs via a ramdisk image (required for the dm-verity signature verification).Build tested on Verdin AM62, Verdin iMX8MP and Colibri iMX6.
Runtime tested on Verdin iMX8MP and Colibri iMX6.