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 1537242 - Create /etc/security/faillock.conf
Summary: Create /etc/security/faillock.conf
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pam
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Dalibor Pospíšil
Parth Shah
Depends On:
Blocks: 1755139
TreeView+ depends on / blocked
Reported: 2018-01-22 18:34 UTC by ralford
Modified: 2021-08-27 22:50 UTC (History)
6 users (show)

Fixed In Version: pam-1.3.1-5.el8
Doc Type: Enhancement
Doc Text:
.`pam_faillock` can now read settings from `faillock.conf` configuration file The `pam_faillock` module, a part of pluggable authentication modules (PAM), can now read settings from the configuration file located at `/etc/security/faillock.conf`. This makes it easier to set up an account lockout on authentication failures, provide user profiles for this functionality, and handle different PAM configurations by simply editing the `faillock.conf` file.
Clone Of:
Last Closed: 2020-04-28 16:42:43 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-25962 0 None None None 2021-08-27 22:43:09 UTC
Red Hat Product Errata RHBA-2020:1780 0 None None None 2020-04-28 16:43:05 UTC

Description ralford 2018-01-22 18:34:39 UTC
Description of problem:
Create /etc/security/faillock.conf and allow the following options to be configured in the faillock.conf file:


Currently, scap-security-guide has complicated remediation scripts that have to add pam_faillock as well as all the options to configure pam to meet all the different customer compliance requirements. This is error prone and cannot handle all the differing customer pam configurations. This would also 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. It would just be a simple change in faillock.conf

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. ls /etc/security/faillock.conf
ls: cannot access '/etc/security/faillock.conf': No such file or directory

2. man pam_faillock
No reference to /etc/security/faillock.conf


Actual results:
/etc/security/faillock.conf does not exist

Expected results:
/etc/security/faillock.conf exists and the following options can be configured:


Additional info:
If this can also be added upstream as well, that would be great.

Comment 2 Simo Sorce 2019-02-11 15:41:48 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 9 Shawn Wells 2019-11-20 17:16:59 UTC
There has not been a public update to this BZ since https://bugzilla.redhat.com/show_bug.cgi?id=1537242#c2. Could a public update be provided? Thanks!

Comment 17 errata-xmlrpc 2020-04-28 16:42: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, and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.