From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: Account Lockouts
Date: Wed, 7 Jan 2009 10:25:27 -0500
Message-ID: <200901071025.28494.sgrubb@redhat.com>
References: <1221782548.6783.30.camel@homeserver>
	<1226089188.7321.128.camel@homeserver>
	<50311B90-F22F-47D7-992D-BF3669ECE227@arlut.utexas.edu>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <50311B90-F22F-47D7-992D-BF3669ECE227@arlut.utexas.edu>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Wednesday 07 January 2009 10:17:54 am Starr-Renee Corbin wrote:
> While the account lockout policy is set, I am unable to figure out the
> syntax for the watches to add to audit.rules that will show the account
> lockout event.  I have to be able to do this for about 150 systems.

pam_tally2 is hardwired to send lockout events to the audit system. Use it 
rather than pam_tally. They will be in the audit logs as ANOM_LOGIN_FAILURES 
when the limit is reached, as RESP_ACCT_LOCK_TIMED for the actual locking of 
the acct, and RESP_ACCT_UNLOCK_TIMED when the acct is unlocked due to time 
expiration or admin action.

-Steve