Bug 1285550 - root lockout exemption for groups
Summary: root lockout exemption for groups
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pam
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Dalibor Pospíšil
Depends On:
TreeView+ depends on / blocked
Reported: 2015-11-25 22:44 UTC by Steve Grubb
Modified: 2018-04-10 11:36 UTC (History)
4 users (show)

Fixed In Version: pam-1.1.8-19.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2018-04-10 11:35:33 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0718 None None None 2018-04-10 11:36:09 UTC

Description Steve Grubb 2015-11-25 22:44:52 UTC
Description of problem:
Security Guidance advises people to not login via root. This is enforced in several places based on the security guides. However, it  looks like if someone/everyone gets locked out, it possibly requires a root login because the is the only account exempt from the lockout policy.

Most admins are members of the wheel group. Security Guidance typically asks admins to fix su or sudo to only allow wheel group members the ability to become root. I am wondering if the lockout exemptions for root should also be optionally extended to wheel group members so that we have a recovery method consistent with security guidance.

Comment 1 Tomas Mraz 2016-01-18 15:29:57 UTC
So what PAM modules are we talking here about?

pam_faillock is clearly one. Is there anything else?

Comment 2 Steve Grubb 2016-01-18 15:50:30 UTC
pam_faillock is the main one. I presume the pam_tally* modules are being deprecated at some future point.

Comment 11 errata-xmlrpc 2018-04-10 11:35:33 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.