From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Draft copy of how to write good events
Date: Wed, 03 Sep 2014 12:24:44 -0400 [thread overview]
Message-ID: <3228354.4toYKCVf1H@x2> (raw)
Hello,
People have mentioned a couple times that they would like to know more about
what is expected of well written events. I put together a draft document
located here:
http://people.redhat.com/sgrubb/audit/audit-events.txt
The intention is to add this to the kernel documentation after people have had
a chance to review it and send feedback. Any and all comments are welcome.
-Steve
next reply other threads:[~2014-09-03 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 16:24 Steve Grubb [this message]
2014-09-04 22:04 ` Draft copy of how to write good events Richard Guy Briggs
2014-09-04 22:08 ` Richard Guy Briggs
2014-09-08 18:35 ` Steve Grubb
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=3228354.4toYKCVf1H@x2 \
--to=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.