From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: aulast only displaying reboot pseudo-users
Date: Wed, 04 Jun 2014 18:23:29 -0400
Message-ID: <11400116.CdDq4vnLvl@x2>
References: <20140605000405.687f6ad7@fornost.bigon.be>
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: <20140605000405.687f6ad7@fornost.bigon.be>
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 Thursday, June 05, 2014 12:04:05 AM Laurent Bigonville wrote:
> On my machine with audit 2.3.6 the following call to aulast is only
> displaying the "reboot" pseudo-users and not the actual logins:
> 
> ausearch --start this-month --raw | aulast --stdin
> 
> Passing the "--bad" option to aulast, seems to correctly return the
> failed login attempt.
> 
> Also, adding the login name to the aulast command doesn't seems to work
> at all even with the --bad option.
> 
> OTOH, the aulastlog command seems to work as expected.
> 
> An idea?

 Would this happen to be a system with a recent GDM and systemd? If so, they 
are known to be messing up the audit trail. I am trying to write a system 
validation test suite to spot issues like this. If you look at gdm, its 
sending duplicate events. Systemd events don't make it to audit all the time. 
Its a mess on the desktop right now.

-Steve