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 1537240 - Add more options to pwquality.conf via rebase to 1.4.4
Summary: Add more options to pwquality.conf via rebase to 1.4.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libpwquality
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 8.4
Assignee: Nobody
QA Contact: Ivan Nikolchev
Khushbu Borole
URL:
Whiteboard:
Depends On:
Blocks: 1894575
TreeView+ depends on / blocked
 
Reported: 2018-01-22 18:09 UTC by ralford
Modified: 2023-12-15 16:01 UTC (History)
7 users (show)

Fixed In Version: libpwquality-1.4.4-1.el8
Doc Type: Enhancement
Doc Text:
.`libpwquality` rebased to 1.4.4 The `libpwquality` package has been rebased to version 1.4.4. This release includes multiple bug fixes and translation updates. Most notably, the following setting options have been added to the `pwquality.conf` file: * `retry` * `enforce_for_root` * `local_users_only`
Clone Of:
Environment:
Last Closed: 2021-05-18 14:49:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:
kborole: needinfo-
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:1605 0 None None None 2021-05-18 14:49:47 UTC

Description ralford 2018-01-22 18:09:45 UTC 
Description of problem:
Currently, retry, enforce_for_root, and local_users_only have to be configured manually in system-auth, password-auth, etc. We are noticing that customers are requiring to add or modify these options in multiple, differing pam files to meet compliance requirements. Also, the scap-security-guide project will most likely have to handle these scenarios in future as it already has to modify the pam files for the retry option. It would be really nice to only have to configure it in /etc/security/pwquality.conf rather than modifying the pam files themselves. This would make authconfig, future authselect, and scap-security-guide less complicated as modifying the pam files, providing profiles, or handling different pam configurations would no longer be required for these options. 

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

How reproducible:
always

Steps to Reproduce:
1. Try to modify these options in /etc/security/pwquality.conf
2.
3.

Actual results:
Any modifications to retry, enforce_for_root, and local_users_only have to be configured manually in system-auth, password-auth, etc.

Expected results:
retry = <some_number> can be configured in /etc/security/pwquality.conf
enforce_for_root = (0|1) can be configured in /etc/security/pwquality.conf
local_users_only = (0|1) can be configured in /etc/security/pwquality.conf

Additional info:
If this can also be added upstream, that would be great.
Comment 2 Simo Sorce 2019-02-11 15:39:24 UTC 
This issue was not selected to be included either in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small amount of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.
Comment 4 Tomas Mraz 2020-04-01 08:45:25 UTC 
This should be handled via rebase to upstream version 1.4.2 which has this feature implemented.

The upstream changes:

Release 1.4.2
* Fix regression in handling retry, enforce_for_root, and
  local_users_only options introduced with the previous
  release.

Release 1.4.1
* pam_pwquality: Abort the retry loop if user requests it.
* Allow setting retry, enforce_for_root, and local_users_only options
  in the pwquality.conf config file.
* Fix uninitialized memory in word distance calculations.
* Fix possible one byte buffer underflow when parsing the config file.
* Return default cracklib dictionary path if not overriden.
* Update translations from Zanata.
Comment 29 errata-xmlrpc 2021-05-18 14:49:43 UTC 
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 (libpwquality bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1605
Note You need to log in before you can comment on or make changes to this bug.