f510a438df
Allowing to boot a non-encrypted rootfs when encryption is enable is a security hole: if an attacker can somehow write (offline) to the media, he could flash a custom unencrypted rootfs and break into the system. If the system is configured to use encryption, only encrypted rootfs will boot. Trying to boot a non-encrypted rootfs will fail and power off the device. https://jira.digi.com/browse/DEL-3829 Signed-off-by: Tatiana Leon <tatiana.leon@digi.com> |
||
|---|---|---|
| .. | ||
| base-files | ||
| busybox | ||
| images | ||
| init-ifupdown | ||
| initscripts | ||
| packagegroups | ||
| psplash | ||
| recovery | ||
| systemd | ||
| sysvinit | ||
| trustfence | ||