public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Matthew Booth <mbooth@redhat.com>
Cc: William Kelly <wkelly@rackspace.com>,
	Bret Piatt <bret.piatt@rackspace.com>,
	linux-audit@redhat.com
Subject: Re: get_field_str() and interpret_field() bug with multi-word fields
Date: Tue, 12 Aug 2008 19:01:23 -0400	[thread overview]
Message-ID: <1218582083.3540.19.camel@localhost.localdomain> (raw)
In-Reply-To: <48A20A60.8000605@redhat.com>

On Tue, 2008-08-12 at 23:10 +0100, Matthew Booth wrote:
> Steve Grubb wrote:
> > If somebody has a better idea/code in hand when we start the 2.0 code, I'd 
> > like to consider it. The pre-requisites are it has to be backward compatible, 
> > it has to handle unicode, it has to handle fields with odd characters.
> 
> I have thought for some time now that the kernel would do better to 
> produce binary records. This would have many advantages, including:
> 
> * Very simple parsing
> * Much faster to parse
> * Faster to produce
> * Much easier to specify
> 
> The production of text would then be the problem of the audit daemon. If 
> the current text based nightmare were frozen, they could even live 
> side-by-side.

I've heard this binary audit data talk before.  What would it actually
look like?

I'm perfectly fine if someone comes up with some patches that make
wholesale interface changes, but you better be d@m^ sure that I can run
that kernel on RHEL5 and it will work.

-Eric

  reply	other threads:[~2008-08-12 23:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 17:49 get_field_str() and interpret_field() bug with multi-word fields Jonathan Kelly
2008-08-12 18:05 ` LC Bruzenak
2008-08-12 18:52   ` John Dennis
2008-08-12 19:02     ` LC Bruzenak
2008-08-12 18:16 ` John Dennis
2008-08-12 21:13   ` Steve Grubb
2008-08-12 22:10     ` Matthew Booth
2008-08-12 23:01       ` Eric Paris [this message]
2008-08-12 19:16 ` Steve Grubb
2008-08-12 19:58   ` John Dennis
2008-08-12 20:11     ` Eric Paris
2008-08-12 20:32       ` Steve Grubb
2008-08-12 21:09         ` John Dennis
2008-08-12 21:24           ` Steve Grubb
2008-08-12 22:37             ` John Dennis
2008-08-13  0:33         ` Klaus Heinrich Kiwi
2008-08-13 15:09           ` Eric Paris
2008-08-13 16:25             ` Klaus Heinrich Kiwi
2008-08-13 17:02               ` Steve Grubb
2008-08-13 17:30                 ` LC Bruzenak
2008-08-13 18:49                 ` Linda Knippers
2008-08-13 19:58                   ` John Dennis
2008-08-14 18:25               ` Stephen Smalley
2008-08-15 13:58                 ` Matteo Michelini
2008-08-15 14:10                   ` Steve Grubb
2008-08-15 15:27                     ` Matteo Michelini
2008-08-15 14:15                   ` Stephen Smalley
2008-08-13 16:29             ` John Dennis
2008-08-13 22:35           ` Casey Schaufler
2008-08-12 20:57       ` John Dennis
2008-08-12 21:18         ` Steve Grubb
2008-08-12 21:40           ` John Dennis
2008-08-12 21:53             ` Steve Grubb
2008-08-12 22:11               ` John Dennis
2008-08-12 22:46                 ` Steve Grubb
2008-08-12 22:59         ` Eric Paris
  -- strict thread matches above, loose matches on Subject: below --
2008-08-13 16:57 Jonathan Kelly

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=1218582083.3540.19.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=bret.piatt@rackspace.com \
    --cc=linux-audit@redhat.com \
    --cc=mbooth@redhat.com \
    --cc=wkelly@rackspace.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