From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: Lockout record
Date: Wed, 1 Dec 2010 16:16:42 -0500
Message-ID: <201012011616.43237.sgrubb@redhat.com>
References: <E2B97F4E65AFD84DA1A7B3BEC35E17140149E6A23530@hailstorm.faac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <E2B97F4E65AFD84DA1A7B3BEC35E17140149E6A23530@hailstorm.faac.com>
List-Unsubscribe: <https://www.redhat.com/mailman/options/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, December 01, 2010 03:01:50 pm Steve M. Zak wrote:
> Does the audit system have a watch that will show account lockouts in real
> time?

You do not need to set any watch, pam sends a RESP_ACCT_LOCK_TIMED event when the 
account is locked. Before that, the account is not locked. It is counting bad 
authentication attempts and sending USER_AUTH events as the user tries to login.
 
> The pam implementation doesn't write to the logs until after the deny=
> number has been exceeded.

Pam writes something every time. It sends 2 different events because a bad auth is not 
a lockout.

-Steve