RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1288108 - SysAdminGuide: grub2 password protection section should be updated
Summary: SysAdminGuide: grub2 password protection section should be updated
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-System_Administrators_Guide
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Maxim Svistunov
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 14:44 UTC by Tomas Hoger
Modified: 2019-03-06 01:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-08 12:40:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomas Hoger 2015-12-03 14:44:29 UTC 
Document URL:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html#sec-Preserving_the_Setup_after_GRUB_2_Updates

Section Number and Name:

24.6. GRUB 2 Password Protection

Describe the issue:

I think there are few issues:

- Document mentions that 01_users should be created if it wasn't during system installation.  It should also mention that the file needs to be made executable to actually get used during grub2-mkconfig.  Similarly, it should suggest safe permissions (e.g. 700) to avoid having password in a world-readable file.

- Well, the above is no longer relevant on 7.2, as 01_users is now packaged and I do not think it's expected to have username / passwords defined in it directly any more.

Instead, the document should mention grub2-setpassword, which was added  in 7.2 (see bug 985962), as the default 01_users now has commands to read password from /boot/grub2/user.cfg generated by that command.

- Document describes how to create custom password protected boot menu entries in 40_custom.  However, it's probably not what most users care about or want to do.  I think the document should explicitly describe impact the creation of superuser has on the default entries generated by the 10_linux (i.e. with superuser defined, it's no longer possible to edit boot command line without providing password, but any boot meny entry can be selected, as all entries generated by 10_linux have --unrestricted).  The following kbase describes how to make grub2 require password during boot:

https://access.redhat.com/solutions/979643
Note You need to log in before you can comment on or make changes to this bug.