Bug 1273373 - Require the option "unlock_time=never" with pam_faillock.so module.
Summary: Require the option "unlock_time=never" with pam_faillock.so module.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pam
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Dalibor Pospíšil
Mirek Jahoda
URL:
Whiteboard:
: 1148042 (view as bug list)
Depends On:
Blocks: 1203710 1296594 1313485 1404832
TreeView+ depends on / blocked
 
Reported: 2015-10-20 10:24 UTC by Chinmay Paradkar
Modified: 2020-01-17 15:35 UTC (History)
14 users (show)

Fixed In Version: pam-1.1.8-15.el7
Doc Type: Enhancement
Doc Text:
*pam_faillock* can be now configured with `unlock_time=never` The *pam_faillock* module now allows specifying using the `unlock_time=never` option that the user authentication lock caused by multiple authentication failures should never expire.
Clone Of:
: 1404832 (view as bug list)
Environment:
Last Closed: 2016-11-04 03:31:39 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2314 normal SHIPPED_LIVE pam bug fix and enhancement update 2016-11-03 13:41:53 UTC

Description Chinmay Paradkar 2015-10-20 10:24:04 UTC 
Description of problem:

The global option "unlock_time" available with "pam_faillock" module does not have an option to lock a user account until it's unlocked by admin.

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

pam-1.1.8-12.el7.x86_64

Additional info:

The current Fedora rawhide version of pam_faillock has this feature "unlock_time=never" but the RHEL-7 package does not. Hence opening a Bug to backport the feature to RHEL-7.
Comment 2 Tomas Mraz 2015-12-14 09:52:14 UTC 
*** Bug 1148042 has been marked as a duplicate of this bug. ***
Comment 13 errata-xmlrpc 2016-11-04 03:31:39 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.

https://rhn.redhat.com/errata/RHBA-2016-2314.html
Note You need to log in before you can comment on or make changes to this bug.