GNU GRUB - Bugs: bug #62380, New special environment variable...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62380: New special environment variable to control default menu security
Submitter: | Steven Stallion <stallion> | ||
Submitted: | Thu 28 Apr 2022 01:17:52 PM UTC | ||
Category: | Security | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Feature Request |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Steven Stallion |
Open/Closed: | Open | Release: | Git master |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
When enabling secure boot, it can be a pain to track down all uses of menuentry and submenu to change security flags (eg. defaulting to --unrestricted).
I'd like to propose a new special environment variable named `menu_security', which defines a default that is applied to a configuration if a security flag is not specified on an entry.
I think this would simplify configuration substantially, especially for files other than 10_linux that do not have a CLASS variable defined.
I have a little bit of time this week - I'll try to put together a candidate patch to see what folks think.