From: Linda Knippers <linda.knippers@hp.com>
To: Karl MacMillan <kmacmillan@mentalrootkit.com>
Cc: Joshua Brindle <method@gentoo.org>,
Joy Latten <latten@austin.ibm.com>,
eparis@parisplace.org, redhat-lspp@redhat.com,
selinux@tycho.nsa.gov, jmorris@namei.org, paul.moore@hp.com,
vyekkirala@TrustedCS.com
Subject: Re: RHEL5 Kernel with labeled networking
Date: Tue, 03 Oct 2006 17:47:37 -0400 [thread overview]
Message-ID: <4522DA79.6080708@hp.com> (raw)
In-Reply-To: <4522D667.5030401@mentalrootkit.com>
Karl MacMillan wrote:
> Linda Knippers wrote:
>
>> Joshua Brindle wrote:
>>
>>
>>> Linda Knippers wrote:
>>>
>>>
>
> <snip>
>
>>>> If we go the auditallow route then we lose some audit record management
>>>> features, like the ability to enable/disble/search for these records,
>>>> don't we? Do we care?
>>>
>>> enable and disable with a boolean
>>>
>>> searching? surely you can search avc records..
>>
>> 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?
There was a discussion a long, long time about about how administrators should
manage what gets into the audit logs, whether its with the audit tools, the
policy or both. There are explicit message types for alot of management
operations so that the admin can decide whether to get them and the tools
make it easy to search for. If changing the ipsec label configuration is just
an AVC message, it will be different from just about everything else. It might
be easy, but is it what we want?
I wish sgrubb were reading mail today. I think this is something that he
cares about, at least he did the last time we had this conversation.
-- ljk
--
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-03 21:47 UTC|newest]
Thread overview: 43+ 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 [this message]
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
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 19:01 Joy Latten
2006-10-03 17:16 Venkat Yekkirala
2006-10-03 0:23 Eric Paris
2006-10-03 15:34 ` Linda Knippers
2006-10-03 15:41 ` Stephen Smalley
2006-10-03 15:51 ` Linda Knippers
2006-10-03 16:12 ` Linda Knippers
2006-10-03 15:45 ` Eric Paris
2006-10-03 16:08 ` James Morris
2006-10-03 16:24 ` Linda Knippers
2006-10-03 16:41 ` James Morris
2006-10-03 16:46 ` Linda Knippers
2006-10-03 16:46 ` Joshua Brindle
2006-10-03 19:29 ` Joshua Brindle
2006-10-03 16:40 ` Paul Moore
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=4522DA79.6080708@hp.com \
--to=linda.knippers@hp.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=kmacmillan@mentalrootkit.com \
--cc=latten@austin.ibm.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.