PAM_FAILLOCK - Online Linux Manual PageSection : 8
Updated : 09/03/2021
Source : Linux-PAM Manual
Note : Linux−PAM Manual
NAMEpam_faillock − Module counting authentication failures during a specified interval
SYNOPSISauth ... pam_faillock.so {preauth|authfail|authsucc} [conf=/path/to/config−file] [dir=/path/to/tally−directory] [even_deny_root] [deny=n] [fail_interval=n] [unlock_time=n] [root_unlock_time=n] [admin_group=name] [audit] [silent] [no_log_info] account ... pam_faillock.so [dir=/path/to/tally−directory] [no_log_info]
DESCRIPTIONThis module maintains a list of failed authentication attempts per user during a specified interval and locks the account in case there were more than deny consecutive failed authentications. Normally, failed attempts to authenticate root will not cause the root account to become blocked, to prevent denial−of−service: if your users aren't given shell accounts and root may only login via su or at the machine console (not telnet/rsh, etc), this is safe.
OPTIONS{preauth|authfail|authsucc} This argument must be set accordingly to the position of this module instance in the PAM stack. The preauth argument must be used when the module is called before the modules which ask for the user credentials such as the password. The module just examines whether the user should be blocked from accessing the service in case there were anomalous number of failed consecutive authentication attempts recently. This call is optional if authsucc is used. The authfail argument must be used when the module is called after the modules which determine the authentication outcome, failed. Unless the user is already blocked due to previous authentication failures, the module will record the failure into the appropriate user tally file. The authsucc argument must be used when the module is called after the modules which determine the authentication outcome, succeeded. Unless the user is already blocked due to previous authentication failures, the module will then clear the record of the failures in the respective user tally file. Otherwise it will return authentication error. If this call is not done, the pam_faillock will not distinguish between consecutive and non−consecutive failed authentication attempts. The preauth call must be used in such case. Due to complications in the way the PAM stack can be configured it is also possible to call pam_faillock as an account module. In such configuration the module must be also called in the preauth stage. conf=/path/to/config−file Use another configuration file instead of the default /etc/security/faillock.conf. The options for configuring the module behavior are described in the faillock.conf(5) manual page. The options specified on the module command line override the values from the configuration file.
MODULE TYPES PROVIDEDThe auth and account module types are provided.
RETURN VALUESPAM_AUTH_ERR An invalid option was given, the module was not able to retrieve the user name, no valid counter file was found, or too many failed logins. PAM_BUF_ERR Memory buffer error. PAM_CONV_ERR The conversation method supplied by the application failed to obtain the username. PAM_INCOMPLETE The conversation method supplied by the application returned PAM_CONV_AGAIN. PAM_SUCCESS Everything was successful. PAM_IGNORE User not present in passwd database.
NOTESConfiguring options on the module command line is not recommend. The /etc/security/faillock.conf should be used instead. The setup of pam_faillock in the PAM stack is different from the pam_tally2 module setup. Individual files with the failure records are created as owned by the user. This allows pam_faillock.so module to work correctly when it is called from a screensaver. Note that using the module in preauth without the silent option specified in /etc/security/faillock.conf or with requisite control field leaks an information about existence or non−existence of a user account in the system because the failures are not recorded for the unknown users. The message about the user account being locked is never displayed for non−existing user accounts allowing the adversary to infer that a particular account is not existing on a system.
EXAMPLESHere are two possible configuration examples for /etc/pam.d/login. They make pam_faillock to lock the account after 4 consecutive failed logins during the default interval of 15 minutes. Root account will be locked as well. The accounts will be automatically unlocked after 20 minutes. In the first example the module is called only in the auth phase and the module does not print any information about the account being blocked by pam_faillock. The preauth call can be added to tell users that their logins are blocked by the module and also to abort the authentication without even asking for password in such case. /etc/security/faillock.conf file example: deny=4
unlock_time=1200
silent
/etc/pam.d/config file example: auth required pam_securetty.so
auth required pam_env.so
auth required pam_nologin.so
# optionally call: auth requisite pam_faillock.so preauth
# to display the message about account being locked
auth [success=1 default=bad] pam_unix.so
auth [default=die] pam_faillock.so authfail
auth sufficient pam_faillock.so authsucc
auth required pam_deny.so
account required pam_unix.so
password required pam_unix.so shadow
session required pam_selinux.so close
session required pam_loginuid.so
session required pam_unix.so
session required pam_selinux.so open
In the second example the module is called both in the auth and account phases and the module informs the authenticating user when the account is locked if silent option is not specified in the faillock.conf. auth required pam_securetty.so
auth required pam_env.so
auth required pam_nologin.so
auth required pam_faillock.so preauth
# optionally use requisite above if you do not want to prompt for the password
# on locked accounts
auth sufficient pam_unix.so
auth [default=die] pam_faillock.so authfail
auth required pam_deny.so
account required pam_faillock.so
# if you drop the above call to pam_faillock.so the lock will be done also
# on non−consecutive authentication failures
account required pam_unix.so
password required pam_unix.so shadow
session required pam_selinux.so close
session required pam_loginuid.so
session required pam_unix.so
session required pam_selinux.so open
FILES/var/run/faillock/* the files logging the authentication failures for users /etc/security/faillock.conf the config file for pam_faillock options
SEE ALSOfaillock(8), faillock.conf(5), pam.conf(5), pam.d(5), pam(8)
AUTHORpam_faillock was written by Tomas Mraz. 0
Johanes Gumabo
Data Size : 20,586 byte
man-pam_faillock.8Build : 2024-12-05, 20:55 :
Visitor Screen : x
Visitor Counter ( page / site ) : 2 / 185,353
Visitor ID : :
Visitor IP : 52.14.173.116 :
Visitor Provider : AMAZON-02 :
Provider Position ( lat x lon ) : 39.962500 x -83.006100 : x
Provider Accuracy Radius ( km ) : 1000 :
Provider City : Columbus :
Provider Province : Ohio , : ,
Provider Country : United States :
Provider Continent : North America :
Visitor Recorder : Version :
Visitor Recorder : Library :
Online Linux Manual Page : Version : Online Linux Manual Page - Fedora.40 - march=x86-64 - mtune=generic - 24.12.05
Online Linux Manual Page : Library : lib_c - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Online Linux Manual Page : Library : lib_m - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Data Base : Version : Online Linux Manual Page Database - 24.04.13 - march=x86-64 - mtune=generic - fedora-38
Data Base : Library : lib_c - 23.02.07 - march=x86-64 - mtune=generic - fedora.36
Very long time ago, I have the best tutor, Wenzel Svojanovsky . If someone knows the email address of Wenzel Svojanovsky , please send an email to johanes_gumabo@yahoo.co.id .
If error, please print screen and send to johanes_gumabo@yahoo.co.id
Under development. Support me via PayPal.