Under Linux operating system you can use the faillog command to display faillog records or to set login failure limits. faillog command displays the contents of the failure log from /var/log/faillog database file. It also can be used for maintains failure counters and limits. If you run faillog command without arguments, it will display only list of user faillog records who have ever had a login failure.
PAM Settings
I found that under RHEL / CentOS Linux 5.x, you need to modify /etc/pam.d/system-auth file. You need to configure a PAM module pam_tally.so. Otherwise faillog command will never display failed login attempts.
PAM Configuration To Recored Failed Login Attempts
pam_tally.so module maintains a count of attempted accesses, can reset count on success, can deny access if too many attempts fail. Edit /etc/pam.d/system-auth file, enter:
# vi /etc/pam.d/system-auth
Modify as follows:
auth required pam_tally.so no_magic_root
account required pam_tally.so deny=3 no_magic_root lock_time=180
Where,
- deny=3 : Deny access if tally for this user exceeds 3 times.
- lock_time=180 : Always deny for 180 seconds after failed attempt. There is also unlock_time=n option. It allow access after n seconds after failed attempt. If this option is used the user will be locked out for the specified amount of time after he exceeded his maximum allowed attempts. Otherwise the account is locked until the lock is removed by a manual intervention of the system administrator.
- magic_root : If the module is invoked by a user with uid=0 the counter is not incremented. The sys-admin should use this for user launched services, like su, otherwise this argument should be omitted.
- no_magic_root : Avoid root account locking, if the module is invoked by a user with uid=0
Save and close the file.
How Do I Display All Failed Login Attempts For a User Called vivek?
Type the command as follows:
# faillog -u vivek
Login Failures Maximum Latest On vivek 3 0 12/19/07 14:12:53 -0600 64.11.xx.yy
Taks: Show Faillog Records For All Users
Type the following command with the -a option:
# faillog -a
Task: Lock Account
To lock user account to 180 seconds after failed login, enter:
# faillog -l 180 -u vivek
# faillog -l 180
Task: Set Maximum Number of Login Failures
The -m option is allows you to set maximum number of login failures after the account is disabled to specific number called MAX. Selecting MAX value of 0 has the effect of not placing a limit on the number of failed logins. The maximum failure count should always be 0 for root to prevent a denial of services attack against the system:
# faillog -M MAX -u username
# faillog -M 10 -u vivek
How do I Reset The Counters Of Login Failures?
The -r option can reset the counters of login failures or one record if used with the -u USERNAME option:
# faillog -r
To reset counter for user vivek, enter:
# faillog -r -u vivek
On large Linux login server, such as University or government research facility, one might find it useful to clear all counts every midnight or week from a cron job.
# crontab -e
Reset failed login recover every week:
@weekly /usr/bin/faillog -r
Save and close the file.
Recommended readings:
=> Read the pam_tally, faillog and pam man pages:
$ man pam_tally
$ man tally
$ man faillog
See also: The Linux-PAM System Administrators Guide
- RSS feed or Weekly email newsletter
- Share to Twitter • Facebook • 24 comments... add one ↓
40 Linux Server Hardening Security Tips [2019 edition]
Linux 25 PHP Security Best Practices For Sys Admins
Linux Failed Login Control: Lock and Unlock User Accounts Using PAM
Top 25 Nginx Web Server Best Security Practices
Test If Linux Server SCSI / SATA / SSD Hard Disk Going Bad
30 Linux System Monitoring Tools Every SysAdmin Should Know
30 Best Sources For Linux / *BSD / Unix Documentation On the Web
| Category | List of Unix and Linux commands |
|---|---|
| File Management | cat |
| Firewall | CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 |
| Network Utilities | dig • host • ip • nmap |
| OpenVPN | CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04 |
| Package Manager | apk • apt |
| Processes Management | bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time |
| Searching | grep • whereis • which |
| User Information | groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w |
| WireGuard VPN | CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04 |
How to enable the same setting in SuSE Linux environment?
lock_time & unlock_time options are not working on redhat 4 (2.6.9-55.0.2.ELsmp). I am getting error message “pam_tally: unknown option; unlock_time=100” and pam_tally: unknown option; lock_time=120. We have pam version : pam-0.77-66.21. Do this version support lock_time & unlock_time options ?
one of the best sites where person like mw can get lot of knowledge
Exactly
Can we exclude PAM modules for certain groups? This is for some particular application group need to disable PAM modules .
At least for CentOS 5 the only valid options for the account phase are magic_root and no_reset, all other should be in the auth phase
Hi, i tried this to add account locked out policy in rhel 5.0 but this is not working
i go to /etc/pam.d/system-auth file and add both lines in it
auth required pam_tally.so no_magic_root
account required pam_tally.so deny=3 no_magic_root lock_time=180
after that i checked faillog -u lalit (username)
it shows faillog but when tried to check it is lock the account or not it is not working
if u have anyother way then please help me ..
Anyone have any Idea why Centos 5.2 would take every login as a failure when setting up for lockout after X failed attempts?
* barney griggs, to lock a user out I’d rather use “faillog”: /usr/bin/faillog -u ACCOUNT -m 10 -l 60
* lalit, you should try remove items from the line: account required pam_tally.so deny=3 no_magic_root lock_time=180
very good
good ……………. 🙂
This contains wrong information, there cannot be deny in Account section of pam_tally.so
all of the above is not working
Do you have faillog in your system? I did not. (I dont know if it should come pre-installed but for me it was not )
The following worked for me,
if you’re using pam_tally use
pam_tally –reset –user
If you’re using pam_tally2, which is typical in rhel6 use
pam_tally2 -r -u
$ vi /etc/pam.d/system-auth
My file doesnt contain mentined lines;
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required pam_env.so
auth sufficient pam_unix.so try_first_pass nullok
#auth sufficient pam_plesk.so try_first_pass
auth required pam_deny.so
account required pam_unix.so
password required pam_cracklib.so try_first_pass retry=3
#password optional pam_plesk.so try_first_pass
password sufficient pam_unix.so try_first_pass use_authtok nullok md5
password required pam_deny.so
session optional pam_keyinit.so revoke
session required pam_limits.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so
Add below two lines to system-auth file
auth required pam_tally.so per_user deny=5 no_magic_root unlock_time=180
password required pam_cracklib.so try_first_pass retry=5 no_magic_root lock_time=180
The above lines used for account lock for 180 Sec and unlock afgter 180 Sec.
Regards,
Hari Mani Kandan.A
Maybe you like this:
denton@tron:~$ ls -slapht /etc/cron.daily/faillog
4,0K -rwxr-xr-x 1 root root 963 14. Nov 2010 /etc/cron.daily/faillog
denton@tron:~$ cat /etc/cron.daily/faillog
+++ +++ +++
# TRON-DELTA.ORG / faillog (ANACRON) / v1.3.02
sAccAll=$(cat /etc/passwd | cut -d”:” -f1)
sAccRem=’root daemon bin sys sync games man lp mail news uucp proxy www-data backup list irc gnats nobody libuuid dhcp syslog klog hplip avahi-autoipd gdm messagebus avahi polkituser haldaemon ntp statd clamav mysql saned debian-tor privoxy festival’
iCounter=1
sCounter=$(wc -l “/etc/passwd” | cut -d ‘ ‘ -f1)
while [ $iCounter -le $sCounter ]
do
slAccAll=$(echo $sAccAll | cut -d ‘ ‘ -f $iCounter)
slAccRem=$(echo $sAccRem | cut -d ‘ ‘ -f $iCounter)
if [ “$slAccAll” != “$slAccRem” ] && [ “$slAccAll” != “” ] && [ “$slAccRem” = “” ]
then
/usr/bin/faillog -u $slAccAll -m 10 -l 60
fi
iCounter=`expr $iCounter + 1`
done
echo “User accounts successfully setup with faillog: $(date)” >> /var/log/cron/security.log
+++ +++ +++
For explaination: That script will execute on a daily basis and set all self-defined accounts with -m 10 -l 60. I wrote it to make sure all accounts of “ordinary” users are configured correctly at all times in way so that no one has to worry about it anymore. There is room for optimization however. 🙂
Thanks one and all, for most valid information.
Write a shell script that checks whether the username and a password entered by a user are correct. The script should only allow a maximum of 3 attempts before locking a user out of the system
please some one help
Thanks for the wonderful doc.
Typo: PAM Configuration To “Recored” Failed Login Attempts
Typo
“Taks”: Show Faillog Records For All Users
How to do the same on RHEL5. I don’t see the locking happening on RHEL5 after making the above changes.
Is it possible in RHEL 6 and above…?