From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: aulast only displaying reboot pseudo-users Date: Tue, 17 Jun 2014 09:29:21 -0400 Message-ID: <2733072.zhBU5hVyYr@x2> References: <20140605000405.687f6ad7@fornost.bigon.be> <20140614135319.18680d6f@fornost.bigon.be> <1402953610.11087.5.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1402953610.11087.5.camel@localhost> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Eric Paris Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Monday, June 16, 2014 05:20:10 PM Eric Paris wrote: > My guess is that userspace just throws away record where it doesn't find > the auid= and ses= and you kernel happens to live in those couple of > months were it had "new-ses" and "new-auid" Was this patch sent to stable? The audit code tries to handle the old way and the new way: https://fedorahosted.org/audit/browser/trunk/tools/aulast/aulast.c#L175 But I thought the patch went to stable to prevent breaking user space. This is only one issue. I am seeing duplicate and missing events between systemd, gdm, and lightdm. > I'd call this a pretty clear userspace bug where it just completely > drops records, even if it can't parse them... That theory can be tested by using: ausearch --start this-week --debug > /dev/null Anything that gets tossed out will be reported to stderr. -Steve