From: Matthew Booth <mbooth@redhat.com>
To: linux-audit@redhat.com
Subject: DWIM audit tools
Date: Mon, 06 Oct 2008 14:59:11 +0100 [thread overview]
Message-ID: <48EA19AF.3070304@redhat.com> (raw)
Has anybody been looking at making writing audit rules a bit more DWIM.
E.g. when the user types:
auditctl -a entry,always -S stat
what they almost certainly meant was:
auditctl -a entry,always -F arch=i386 -S oldstat -S oldfstat -S ustat -S
oldlstat -S stat -S lstat -S fstat -S stat64 -S lstat64 -S fstat64
auditctl -a entry,always -F arch=x86_64 -S stat -S fstat -S lstat -S
ustat [1]
It would be really helpful if this kind of knowlege was encapsulated
somewhere. If you were going to put it into auditctl, I suspect you'd
want a separate switch for it so you could still be specific if you
needed it. Is anybody looking at anything like this?
Matt
[1] If anybody points out an error in here, they're just making my point
for me :P
--
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services
M: +44 (0)7977 267231
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
reply other threads:[~2008-10-06 17:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48EA19AF.3070304@redhat.com \
--to=mbooth@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