@norbu It's important to minimize what we sign for secure boot and make choices. We need to minimize the attack surface, and everyone can use ext2 for /boot really.
The default signed binaries need to be opinionated. If you have different opinions, sign your own or don't run secure boot.
@norbu revocations are a very complex process. The rotation is quick, but the revocation is very hard.
And yes, we expect substantially higher risk from file systems other than fat and ext2, especially btrfs and zfs.
Also the risks are additive. The more you sign the more places that can have security vulnerabilities.
Hence unnecessary file systems and stuff like themes and images need to go (or you sign themes and images but we don't have that, and themes are a horrible UX vs flicker free).
@realmurphy optimally we make /boot a FAT partition and add native EFI fs drivers to grub and then you get (efidisk0,part1) or something and we can drop all disk, fs drivers.
But it's blocked on moving kernels out of there which is ongoing, and clearly needs some transition.
Add comment