From: John Dennis <jdennis@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Cooked audit log format
Date: Tue, 13 May 2008 08:30:05 -0400 [thread overview]
Message-ID: <482989CD.5070804@redhat.com> (raw)
In-Reply-To: <1210625783.3228.42.camel@localhost.localdomain>
Eric Paris wrote:
> On Mon, 2008-05-12 at 12:12 -0400, John Dennis wrote:
>> It should also be a goal that correct parsing of audit logs not be
>> dependent on specific kernel versions.
>
> I've heard you say this a number of times. Can you let me know specific
> examples of what you had to code around due to specific kernel versions
> since the audit system started to settle down?
The set of strings which are encoded in hex vary depending on kernel
version. That set of special audit fields currently must be hard coded
into any code which attempts to parse audit output or the parsing will
fail, sometimes catastrophically. A list of these special field values
differing between two popular kernel versions has been previously posted
to this list. That list is not complete. If the rules for string
encoding were proper and regular this issue would not exist.
--
John Dennis <jdennis@redhat.com>
next prev parent reply other threads:[~2008-05-13 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 21:40 Cooked audit log format Matthew Booth
2008-05-12 14:43 ` Steve Grubb
2008-05-12 15:02 ` Matthew Booth
2008-05-12 15:19 ` Steve Grubb
2008-05-12 15:50 ` LC Bruzenak
2008-05-12 16:09 ` Miloslav Trmač
2008-05-12 16:34 ` Steve Grubb
2008-05-12 16:44 ` LC Bruzenak
2008-05-12 16:53 ` Matthew Booth
2008-05-12 16:12 ` John Dennis
2008-05-12 20:56 ` Eric Paris
2008-05-13 12:30 ` John Dennis [this message]
2008-05-15 10:28 ` Tony Jones
2008-05-15 12:44 ` Steve Grubb
2008-05-15 15:59 ` John Dennis
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=482989CD.5070804@redhat.com \
--to=jdennis@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-audit@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