#3597 PR open: grub2: remove broken/redundant "Secure Boot entry" with linuxefi/initrdefi commands

Labels: cleanup

lzaoral opened issue at 2026-04-01 17:52:

Pull Request Details:

  • Type: Bug Fix

  • Impact: Normal

  • Reference to related issue (URL): https://github.com/rear/rear/issues/3423

  • How was this pull request tested? x86_64 VM with UEFI and Secure Boot enabled

  • Description of the changes in this pull request:

These commands were a legacy workaround applied to GRUB2 downstream by selected Linux distros on i386/x86_64 to support secure boot. Modern, GRUB2 supports secure boot using the upstream native linux/initrd commands. Several distros still provide linuxefi/initrdefi as mere aliases to linux/initrd for backwards compatibility (e.g. RHEL 8+/SUSE). However, others have dropped them already (e.g. Debian and its derivatives). This makes the rear_secure_boot entry misleading/redundant in the first case, and completely broken in the latter.

Moreover, GRUB2 for other EFI-enabled architectures (e.g. aarch64 or riscv64) has never supported these commands (upstream nor downstream), therefore, the rear_secure_boot entry is broken there as well.

Assisted-by: Cursor with Claude Opus 4.6

codacy-production commented at 2026-04-01 17:54:

Up to standards ✅

🟢 Issues 0 issues >
> > **Results:** > `0` new issues > > [View in > Codacy](https://app.codacy.com/gh/rear/rear/pull-requests/3597/issues) >

TIP This summary will be updated as you push new changes. Give us feedback

[Export of Github issue for rear/rear.]