Practical Application of Verified Boot
summary
Explains how to cryptographically verify bootloader, kernel and filesystem using concrete tools: signing.bbclass in Yocto, NXP CST for bootloader signing, a to-be-upstreamed fitimage class for kernel verification and dm-verity for filesystem integrity. Shows using a Nitrokey HSM / PKCS#11 during CI builds, warns that burning fuses is irreversible, and details operational pitfalls: provisioning factories, CI leaking release keys, field-return procedures, GPLv3 unlock requirements, and the need for thorough documentation and handover.
AI-written summary · about
chapters (13)
- 0:00Verified boot concepts
- 1:06Verified boot complexity
- 3:54ARM verified boot implementations
- 5:58Verified boot case study
- 8:30PKCS#1 and HSMs for secure boot
- 12:23Project knowledge handover
- 15:51Key management challenges
- 18:45Bootloader security trade-offs
- 21:54Documentation for verified boot
- 24:49Field return device handling
- 26:54Yocto HSM signing
- 28:20Conclusion and recommendations
- 29:25Q&A
related talks
42mPractical Application of Verified Boot
49mSecure Boot from A to Z
48mVerified Boot on ARM
42mBecoming a tyrant: Implementing secure boot in embedded devices
48mVerified Boot on Chrome OS and How to do it yourself
45mUsing Secure Boot for the powers of good
46mEnhancing System Security by Integrating Zephyr Bootloader and MCUboot
55mVerified Boot: From ROM to Userspace