From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Draft copy of how to write good events
Date: Mon, 08 Sep 2014 14:35:39 -0400 [thread overview]
Message-ID: <1602023.AXj9xOFLuL@x2> (raw)
In-Reply-To: <20140904220806.GB26201@madcap2.tricolour.ca>
On Thursday, September 04, 2014 06:08:06 PM Richard Guy Briggs wrote:
> > I assume the mix of new-, new_, old- and old_ are there due to
> > historical raisins and changing them would break userspace...
Yes it would. It can break more than ausearch. For example, there could be an
analysis script that does this:
while au.parse_next_event():
if au.find_field("new_gid"):
do_something()
Changing the event would cause the program to not find the event it was looking
for.
> > Here's a unified diff of a few obvious minor cleanups...
I took most of these changes and added some more changes of my own. A revised
copy has been uploaded.
-Steve
prev parent reply other threads:[~2014-09-08 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 16:24 Draft copy of how to write good events Steve Grubb
2014-09-04 22:04 ` Richard Guy Briggs
2014-09-04 22:08 ` Richard Guy Briggs
2014-09-08 18:35 ` 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=1602023.AXj9xOFLuL@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@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