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.

+++ This bug was initially created as a clone of Bug #588893 +++

Description of problem:
Pam does not currently enforce password restrictions on root.

Version-Release number of selected component (if applicable):
pam-1.1.8-6.el7

How reproducible:
100%

Steps to Reproduce:
1. TESTUSER=ROOT /CoreOS/pam/Sanity/pam_cracklib

What does the /CoreOS/pam/Sanity/pam_cracklib test tests? Does it set up pam_cracklib with the enforce_for_root option?

(In reply to Tomas Mraz from comment #3)
> What does the /CoreOS/pam/Sanity/pam_cracklib test tests? Does it set up
> pam_cracklib with the enforce_for_root option?

Yes, you can see it in https://beaker.engineering.redhat.com/tasks/executed?recipe_task_id=19195364 TESTOUT.log there is whole config printed.

Should the config be different from RHEL6?

Look at the configuration files - they are completely meaningless. They put the pam_cracklib at the end of the password stack which means that it is not called at all. You have to replace the pam_pwquality call with the pam_cracklib call instead.

Taking back. I found out that the test assumed presence of cracklib on config file and so it placed those relevant option at the end of the config file which caused the issue.