From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Chris Wright <chrisw@osdl.org>,
David Woodhouse <dwmw2@infradead.org>,
Ondrej Zary <linux@rainbow-software.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] Syscall auditing - move "name=" field to the end
Date: Thu, 17 Mar 2005 13:37:01 -0500 [thread overview]
Message-ID: <200503171337.01433.sgrubb@redhat.com> (raw)
In-Reply-To: <20050317175703.GE28536@shell0.pdx.osdl.net>
On Thursday 17 March 2005 12:57, Chris Wright wrote:
> Steve, are you working on processing log data, do you have a preference?
Yes, I am working on a utility to process the data. I have 4 comments:
1) Fields that magically appear and dissappear are problematic for fast
parsing.
2) There should be a way to control what fields the kernel emits. The
dissappearing fields are what I take to be a stab at message compression. By
having a mask driven approach and always emitting those fields, we can parse
faster and have compression.
3) Fields that potentially have a space, tab, or carriage return in them need
escaping or quoting if they are sent in human readable format.
4) There should be a mode/format status variable so that in the future we can
tell the kernel to switch to another (binary) format. This way human readable
records can go to syslog and special apps like the audit daemon can switch to
another format (binary data ?) which might be more efficient. I haven't spent
anytime looking at what makes sense for a binary format, nor do we have time
for that right now. But I'd like to look at that in the future.
-Steve Grubb
prev parent reply other threads:[~2005-03-17 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 21:34 [patch] Syscall auditing - move "name=" field to the end Ondrej Zary
2005-03-16 22:41 ` Chris Wright
2005-03-17 2:25 ` David Woodhouse
2005-03-17 17:57 ` Chris Wright
2005-03-17 18:37 ` Steve Grubb [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=200503171337.01433.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=chrisw@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
/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