Comments on: HowTo: Configure Linux To Track and Log Failed Login Attempt Records

By: krishna

krishna — Mon, 13 Jun 2011 07:36:34 +0000

good ……………. :)

By: dinesh kumart

dinesh kumart — Sat, 16 Apr 2011 03:14:52 +0000

very good

By: barney griggs

barney griggs — Wed, 09 Jun 2010 22:13:11 +0000

Anyone have any Idea why Centos 5.2 would take every login as a failure when setting up for lockout after X failed attempts?

By: lalit

lalit — Mon, 21 Dec 2009 05:51:44 +0000

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 ..

By: mjp

mjp — Mon, 10 Nov 2008 23:05:23 +0000

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

By: Vasudeva

Vasudeva — Fri, 11 Apr 2008 20:27:15 +0000

Can we exclude PAM modules for certain groups? This is for some particular application group need to disable PAM modules .

By: vijay mane

vijay mane — Tue, 04 Mar 2008 07:58:12 +0000

one of the best sites where person like mw can get lot of knowledge

By: Vasudeva

Vasudeva — Mon, 03 Mar 2008 20:59:20 +0000

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 ?

By: Atanu Banerjee

Atanu Banerjee — Tue, 01 Jan 2008 11:01:40 +0000

How to enable the same setting in SuSE Linux environment?