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.

Nils Ratusznik:

The typos I noticed at the moment are in chapter 4.1.1.2, "Forcing Strong Passwords", in example 4.1. This example recommends to add some lines to the /etc/security/pwquality.conf file to force strong passwords. These lines are:

minlen=8
minclass=4
maxsequence=3
maxrepeat=3

However, my testing did not work. Comments in the file use spaces between variables and values, so I modified them like this:

minlen = 8
minclass = 4
maxsequence = 3
maxrepeat = 3

After this modification, password enforcing policies are now in effect.

This is terribly brittle behaviour; logged https://bugzilla.redhat.com/show_bug.cgi?id=1259633 to try to deal with this at the software level as well.

Fixed in http://jenkinscat.gsslab.pnq.redhat.com:8080/view/RHEL7/job/doc-Red_Hat_Enterprise_Linux-7-Security_Guide%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#sec-Forcing_Strong_Passwords

Will be closed when docs go live on the CP.

The updated guide is live on the portal.