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.

Description of problem:

faillock command does not read options in faillock.conf

"dir" option is set in /etc/security/faillock.conf:
   - dir=/var/log/faillock

pam_faillock locks/unlocks users correctly (i.e.reads/writes user activity files in the customized location)

However, faillock command does not read that option. Instead, a flag must be passed to the command. i.e. faillock --dir /var/log/faillock/


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

pam-1.3.1-14.el8.x86_64

How reproducible:
Always

Steps to Reproduce:

RHEL 8.4

=== Enable faillock ===
authselect select sssd --force
authselect enable-feature with-faillock


=== Set SELinux file context ===
semanage fcontext -a -t faillog_t "/var/log/faillock(/.*)?"
restorecon -Rv /var/log/faillock

=== add below line to /etc/security/faillock.conf ===
dir=/var/log/faillock

Actual results:
faillock command does not read option in config file

Expected results:
faillock (command) and pam_faillock (PAM module) should read the same config file.

Additional info:

Thank you for your confirmation.

It is reasonable to expect pam_faillock (PAM Module) and faillock (command) behave the same way.

master:
    pam_faillock: move config to its own file - 9bcbe96d9e82a23d983c0618178a8dc25596ac2d
    faillock: load configuration from file - fc867a9e22eac2c9a0ed0577776bba4df21c9aad

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 (pam 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-2022:7723