El 6/9/24 a las 15:15, Askar Safin escribió:
Hi. I propose changing "efi" to "EFI" in grub-mkrescue, because this is needed
for secure boot. Please, apply patch below. Here is why.
(...)
I CC Adrian, because I think the problem I talk about is the problem, which
prevented supergrubdisk from making image for CD with secure boot support (
https://github.com/supergrub/supergrub/commit/25414fcbbcb47c1d8616fa18d20409d570145b8f
).
No, I did not disable the SecureBoot support in Super Grub2 Disk because
of this "efi" to "EFI" supposed problem that you describe.
Back in the day I added that commit on the supergrub history because I
wasn't proud enough of the SecureBoot implementation or I messed up in
which branch I was pushing those changes.
Right now the SecureBoot build is turned on on the main supergrub codebase.
It is based on the Debian binaries and, if I'm being honest, I might
remove it (and suggest people to boot Super Grub2 Disk while SecureBoot
is disabled) in the future because of two main reasons:
- Not being able to keep up with Debian updates in order to avoid
problems with revoked SecureBoot-enabled shims/grubs .
- Nobody seem to be asking for any Fedora / RedHat / SusE, you-name-it
SecureBoot support for Super Grub2 Disk.
Alternatively I could try to embed supergrub scripts onto an official
Debian grub-related package and... just recommend that when you cannot
turn off SecureBoot on your UEFI Firmware.
You want SecureBoot's SuperGrub in SusE ? Just port that package onto
SusE yourself.
Note: In this message: SuperGrub = Super Grub Disk = Super Grub2 Disk .
adrian15
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
