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 2069177 - Remediations using faillock should update /etc/security/faillock.conf and use authselect
Summary: Remediations using faillock should update /etc/security/faillock.conf and use...
Keywords:
Status: CLOSED DUPLICATE of bug 1956972
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marcus Burghardt
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-28 12:32 UTC by Dávid Halász
Modified: 2022-04-04 17:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-04 17:00:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-116972 0 None None None 2022-03-28 12:47:49 UTC

Description Dávid Halász 2022-03-28 12:32:07 UTC 
Description of problem:
The remediations that use faillock (Set Deny/Interval/Lockout Time for Failed Password Attempts) should update /etc/security/faillock.conf and use authselect to set the with-faillock feature (per the RHEL8 section here: https://access.redhat.com/solutions/62949). The settings as remediated would not allow logins to an AD realm using sssd. I wasn't able to figure out why exactly. The offending line is the default=die control. I believe it also causes authselect to complain that the files have been modified. Setting the options in the faillock.conf and using authselect to enable the feature seems to have resolved the login issue and has faillock working as expected. I'm guessing the compliance check will fail if it is expecting the options to be in the pam.d files, so that would need to be updated as well.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
https://issues.redhat.com/browse/CRCFEEDBK-427
Comment 2 Marcus Burghardt 2022-04-04 17:00:07 UTC 

*** This bug has been marked as a duplicate of bug 1956972 ***
Note You need to log in before you can comment on or make changes to this bug.