** Description changed: - Currently, the Ubuntu patches for secureboot support will boot the - kernel via the EFI stub ONLY if secureboot is enabled. This means that - if secureboot is disabled, grub wrongly skips the kernel's EFI stub, - resulting in buggy behavior (missing EFI fixups; lack of access to the - TCG log). + [SRU Justification] + Currently, the Ubuntu patches for secureboot support will boot the kernel via the EFI stub ONLY if secureboot is enabled. This means that if secureboot is disabled, grub wrongly skips the kernel's EFI stub, resulting in buggy behavior (missing EFI fixups; lack of access to the TCG log). When booted on EFI, grub should ALWAYS use the EFI protocol to boot the kernel, and only do a non-EFI boot as a fallback if the EFI stub is not available AND secureboot is not enabled. Patches available at https://people.canonical.com/~chrisccoulson/grub- efi-fixes/ + + [Regression potential] + This changes behavior of how grub passes control to Linux kernels when secureboot is disabled on UEFI systems, which can result in arbitrary changes to the boot process up to and including failure to boot if there are bugs in the kernel EFI stub on some platforms. However, it is generally more correct to boot via the EFI stub and it's expected that most users are booting via the EFI stub on UEFI systems due to the ubiquity of SecureBoot by default on modern hardware, so having consistent behavior whether SecureBoot is on or off is likely to be the less buggy option generally.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864533 Title: grub wrongly booting via bios entry point instead of efi when secureboot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1864533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
