From: Steve Grubb <sgrubb@redhat.com>
To: redhat-lspp@redhat.com
Cc: Karl MacMillan <kmacmillan@mentalrootkit.com>,
Linda Knippers <linda.knippers@hp.com>,
Joshua Brindle <method@gentoo.org>,
Joy Latten <latten@austin.ibm.com>,
vyekkirala@TrustedCS.com, jmorris@namei.org, paul.moore@hp.com,
selinux@tycho.nsa.gov, eparis@parisplace.org
Subject: Re: [redhat-lspp] Re: RHEL5 Kernel with labeled networking
Date: Wed, 4 Oct 2006 12:34:20 -0400 [thread overview]
Message-ID: <200610041234.20175.sgrubb@redhat.com> (raw)
In-Reply-To: <4522D667.5030401@mentalrootkit.com>
On Tuesday 03 October 2006 17:30, Karl MacMillan wrote:
> > I meant with the audit tools, so using auditctl to add/remove rules and
> > ausearch for looking for specific record types.
>
> As I said in my other mail the searching should be fine. Why does the
> addition or removal need to be handled by auditctl?
Because we want to teach admins to use the audit system to...audit. Its really
awkward to tell them that you can audit almost everything, but if you need to
do this one other thing, you need to change your policy to do it.
Also, the audit system records changes to itself so that you can see when that
rule disappeared from the config. Doing it in policy, all you get a policy
loaded message which doesn't tell you what in the policy changed.
-Steve
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-10-04 16:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 18:37 RHEL5 Kernel with labeled networking Joy Latten
2006-10-03 19:18 ` Joshua Brindle
2006-10-03 19:16 ` Joy Latten
2006-10-03 20:40 ` Linda Knippers
2006-10-03 21:25 ` Joshua Brindle
2006-10-03 21:27 ` Linda Knippers
2006-10-03 21:30 ` Karl MacMillan
2006-10-03 21:47 ` Linda Knippers
2006-10-03 22:40 ` Joshua Brindle
2006-10-03 22:59 ` Linda Knippers
2006-10-03 23:38 ` [redhat-lspp] " Casey Schaufler
2006-10-05 22:47 ` Klaus Weidner
2006-10-06 10:49 ` Joshua Brindle
2006-10-06 16:45 ` Karl MacMillan
2006-10-04 14:57 ` Stephen Smalley
2006-10-04 15:20 ` Linda Knippers
2006-10-04 17:41 ` [redhat-lspp] " Klaus Weidner
2006-10-04 17:51 ` Eric Paris
2006-10-04 17:57 ` Linda Knippers
2006-10-04 17:57 ` Stephen Smalley
2006-10-04 17:56 ` Stephen Smalley
2006-10-04 16:34 ` Steve Grubb [this message]
2006-10-03 21:28 ` Karl MacMillan
2006-10-03 21:26 ` [redhat-lspp] " Klaus Weidner
2006-10-04 16:25 ` Steve Grubb
2006-10-04 16:39 ` George C. Wilson
2006-10-04 16:13 ` Steve Grubb
2006-10-04 16:28 ` Karl MacMillan
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 18:41 Venkat Yekkirala
2006-10-04 22:18 ` Joy Latten
2006-10-05 14:49 ` Joshua Brindle
2006-10-03 0:23 Eric Paris
2006-10-03 15:34 ` Linda Knippers
2006-10-03 15:45 ` Eric Paris
2006-10-03 16:08 ` James Morris
2006-10-04 14:09 ` [redhat-lspp] " Stephen Smalley
2006-10-04 19:04 ` Daniel J Walsh
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=200610041234.20175.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=kmacmillan@mentalrootkit.com \
--cc=latten@austin.ibm.com \
--cc=linda.knippers@hp.com \
--cc=method@gentoo.org \
--cc=paul.moore@hp.com \
--cc=redhat-lspp@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.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.