From: Steve Grubb <sgrubb@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-audit@redhat.com
Subject: Re: SELinux for auditing
Date: Thu, 1 Feb 2007 10:40:48 -0500 [thread overview]
Message-ID: <200702011040.48405.sgrubb@redhat.com> (raw)
In-Reply-To: <1170341940.12293.124.camel@moss-spartans.epoch.ncsc.mil>
On Thursday 01 February 2007 09:59, Stephen Smalley wrote:
> > Assuming current generation of audit code...
> >
> > auditctl -a exit,always -F perm=w -F obj_type=sbin_t -k executables
>
> Hmmm...on FC6, that yields an error from auditctl:
> key option needs a watch or syscall given prior to it
Ooops, that should be:
auditctl -a exit,always -F perm=w -F obj_type=bin_t -F key=executable
> Dropping the -k option avoids the error message, but overwriting a bin_t
> file doesn't generate any audit message. Similarly, adding a -S open
> avoids the error message while retaining the -k, but overwriting a bin_t
> file doesn't generate any audit message. Not sure where the problem
> lies there.
OK, we should look into this.
> Also, he mentioned RHEL 4 as his platform, so I would tend to think that
> his kernel and auditctl wouldn't support this anyway.
If so, it won't.
> So he may be limited to using auditallow statements in policy, which is
> certainly legitimate use of them (although I understand your goal of
> centralizing audit configuration).
Well, not just centralizing configuration, but that its actually fit for its
purpose. :)
-Steve
next prev parent reply other threads:[~2007-02-01 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 0:11 SELinux for auditing Matthew Booth
2007-02-01 14:36 ` Steve Grubb
2007-02-01 14:59 ` Stephen Smalley
2007-02-01 15:40 ` Steve Grubb [this message]
2007-02-02 12:37 ` Matthew Booth
2007-02-02 20:12 ` Steve Grubb
2007-02-17 0:14 ` 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=200702011040.48405.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sds@tycho.nsa.gov \
/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