Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When applying CIS Level 2 - Server security profile during RHEL 9.1 installation the password encryption algorithm is configured twice and it's unclear which one would be used:
password sufficient pam_unix.so yescrypt shadow use_authtok sha512
This should obviously read (when sha512 is wanted):
password sufficient pam_unix.so sha512 shadow use_authtok
Version-Release number of selected component (if applicable):
RHEL 9.1
Sorry, I got confused with my test systems. The issue is real but comes up only after oscap remediation.
RHEL 9.1 default installation:
password sufficient pam_unix.so try_first_pass use_authtok nullok sha512 shadow
RHEL 9.1 CIS Level 2 Server installation:
password sufficient pam_unix.so yescrypt shadow nullok use_authtok
After remediating with oscap(8) using the "cis" profile shown below.
RHEL 9.1 default installation + oscap/cis remediation:
password sufficient pam_unix.so sha512 shadow nullok use_authtok
RHEL 9.1 CIS Level 2 Server installation + oscap/cis remediation:
password sufficient pam_unix.so yescrypt shadow nullok use_authtok sha512
For both authselect reports the same:
# authselect current -r ; authselect check ;
custom/hardening with-faillock
Current configuration is valid.
And for the latter both sha512/yescrypt are present in the authselect template unconditionally.
Thanks.
Comment 5RHEL Program Management
2023-08-17 14:26:27 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6RHEL Program Management
2023-08-25 16:55:56 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.