From: Eric Paris <eparis@redhat.com>
To: Paul Moore <paul.moore@hp.com>
Cc: linux-audit@redhat.com
Subject: Re: Kernel audit output is inconsistent, hard to parse
Date: Wed, 30 Jan 2008 11:41:08 -0500 [thread overview]
Message-ID: <1201711268.2801.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1201711146.2801.28.camel@localhost.localdomain>
On Wed, 2008-01-30 at 11:39 -0500, Eric Paris wrote:
> And although interesting, this isn't 'broken', so it is
NOT
> the number one
> thing on my infinitely long list of stuff to look at...
>
> -Eric
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2008-01-30 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 22:56 Kernel audit output is inconsistent, hard to parse John Dennis
2008-01-29 23:37 ` Miloslav Trmac
2008-01-30 1:15 ` John Dennis
2008-01-30 14:21 ` Steve Grubb
2008-01-30 15:34 ` Paul Moore
2008-01-30 16:01 ` Steve Grubb
2008-01-30 16:35 ` Paul Moore
2008-01-30 16:39 ` Eric Paris
2008-01-30 16:41 ` Eric Paris [this message]
2008-01-30 16:19 ` John Dennis
2008-01-30 14:26 ` Paul Moore
2008-01-30 16:30 ` Eric Paris
2008-01-30 17:43 ` John Dennis
2008-01-31 21:11 ` Linda Knippers
2008-01-31 21:21 ` Steve Grubb
2008-01-31 21:59 ` Paul Moore
2008-01-31 22:43 ` Casey Schaufler
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=1201711268.2801.30.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul.moore@hp.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