From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul.moore@hp.com>, linux-audit@redhat.com
Subject: Re: Kernel audit output is inconsistent, hard to parse
Date: Thu, 31 Jan 2008 14:43:32 -0800 (PST) [thread overview]
Message-ID: <249330.697.qm@web36615.mail.mud.yahoo.com> (raw)
In-Reply-To: <200801311659.28042.paul.moore@hp.com>
--- Paul Moore <paul.moore@hp.com> wrote:
> On Thursday 31 January 2008 4:21:37 pm Steve Grubb wrote:
> > On Thursday 31 January 2008 16:11:38 Linda Knippers wrote:
> > > At one time we talked about converting to a binary record format.
> >
> > At this point, I want things stable. I've spent the last 3 years working on
> > the foundation to the audit system and we need to focus higher up the stack
> > for a while. There's all kinds of neat things we can do if we don't keep
> > reworking the bottom layer. :)
>
> ... Neat things like building castles on the sand? ;)
>
> (Sorry, couldn't resist!)
There's also the conversion from SELinux interfaces to LSM interfaces
that I'll be revisiting before long. Always a pain to have to do
something like that during a rewrite.
Casey Schaufler
casey@schaufler-ca.com
prev parent reply other threads:[~2008-01-31 22:44 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
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 [this message]
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=249330.697.qm@web36615.mail.mud.yahoo.com \
--to=casey@schaufler-ca.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