From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: William Kelly <wkelly@rackspace.com>,
linux-audit@redhat.com, Bret Piatt <bret.piatt@rackspace.com>
Subject: Re: get_field_str() and interpret_field() bug with multi-word fields
Date: Wed, 13 Aug 2008 12:30:27 -0500 [thread overview]
Message-ID: <1218648627.7022.133.camel@homeserver> (raw)
In-Reply-To: <200808131302.05804.sgrubb@redhat.com>
On Wed, 2008-08-13 at 13:02 -0400, Steve Grubb wrote:
>
>
> There is a problem with any format. How would changing to binary help
> when we realize that we forgot auid in CONFIG_CHANGE? The only thing
> that might help is to stab a version number into each record because
> its size is going to change. This is going to lead to much more
> complex code in the parser.
I was thinking along those lines also - that if there was an identifier
embedded in the audit data that the parser could read, it could know if
it could parse it or not.
Then the matching parser format could be used if it were separated out
as a plugin. Not sure it would need to be each record but maybe just in
the auditd start event?
Maybe this isn't really practicable per se, but if there is a way to
future-proof the data/format pair rather than maintain perpetual
backwards compatibility over advancements I'd think it worthwhile.
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2008-08-13 17:30 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
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 [this message]
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=1218648627.7022.133.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=bret.piatt@rackspace.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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