From: LC Bruzenak <lenny@magitekltd.com>
To: "Miloslav Trmač" <mitr@redhat.com>
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: [PATCH] Handle timestamp 0.0 in auparse, was Re: audit-viewer help needed
Date: Mon, 22 Sep 2008 20:04:43 -0500 [thread overview]
Message-ID: <1222131883.6513.92.camel@homeserver> (raw)
In-Reply-To: <1222131479.2685.92.camel@amilo>
On Tue, 2008-09-23 at 02:57 +0200, Miloslav Trmač wrote:
> LC Bruzenak píše v Po 22. 09. 2008 v 19:38 -0500:
> > On Mon, 2008-09-22 at 23:30 +0000, Miloslav Trmač wrote:
...
>
> I think I can see what's going on. Those are kernel threads; when they
> are created, an audit context is created and zeroed. The timestamp is
> set on system call entry in ordinary threads, but there is no system
> call entry in kernel threads, so the original zero timestamp is used in
> all audit records related to kernel threads.
>
> I'm not sure how to fix it, though. Perhaps identify "operation start"
> points in kernel threads, and update the timestamps in their audit
> contexts at that time?
> Mirek
>
OK; excellent summary!
The bad thing IMO is that ausearch doesn't show these records.
It just drops them (and exits with exit value = 1).
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2008-09-23 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 0:02 audit-viewer help needed LC Bruzenak
[not found] ` <1221812917.2947.10.camel@amilo>
[not found] ` <1221830658.6513.4.camel@homeserver>
2008-09-22 23:30 ` [PATCH] Handle timestamp 0.0 in auparse, was " Miloslav Trmač
2008-09-23 0:38 ` LC Bruzenak
2008-09-23 0:57 ` Miloslav Trmač
2008-09-23 1:04 ` LC Bruzenak [this message]
2008-10-18 15:51 ` Steve Grubb
2008-11-07 20:19 ` LC Bruzenak
2009-01-07 15:17 ` Account Lockouts Starr-Renee Corbin
2009-01-07 15:25 ` Steve Grubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1222131883.6513.92.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
--cc=mitr@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox