Red Hat Bugzilla – Bug 854652
Documentation is not generated properly during build
Last modified: 2013-11-21 15:46:50 EST
Description of problem:
The grub.conf file can include a "password" command which can use "--encrypted" as an option. The documentation that comes in the grub RPM documents "password" but does not mention the "--encrypted" option. With RHEL 5.* there was no such option, it is new with RHEL 6.*
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. $ info -f grub.info -n password
Read the resulting text and see no mention of the --encrypted option.
Read the resulting text and see the --encrypted option mentioned.
If you want to see the --encrypted option try:
$ strings /boot/grub/stage2 | grep encrypted
password [--md5|--encrypted] PASSWD [FILE]
If used in the first section of a menu file, disable all interactive editing control (menu entry editor and command line). If the password PASSWD is entered, it loads the FILE as a new config file and restarts the GRUB Stage 2. If you omit the argument FILE, then GRUB just unlocks privileged instructions. You can also use it in the script section, in which case it will ask for the password, before continueing. The option --md5 tells GRUB that PASSWD is encrypted with md5crypt, --encrypted that PASSWD is encrypted (with algorithm specified in PASSWD: supported is md5, sha-256, sha-512).
Created attachment 731849 [details]
Add --encryption in grub.info
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Reproduced on RHEL6.4 x86_64 Client.
Verified fix on RHEL6.5-20131004.5 x86_64 Client.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.