All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: redhat-lspp@redhat.com, Linda Knippers <linda.knippers@hp.com>,
	Joy Latten <latten@austin.ibm.com>,
	paul.moore@hp.com, vyekkirala@TrustedCS.com, jmorris@namei.org,
	selinux@tycho.nsa.gov, Joshua Brindle <method@gentoo.org>,
	eparis@parisplace.org
Subject: Re: [redhat-lspp] Re: RHEL5 Kernel with labeled networking
Date: Wed, 04 Oct 2006 12:28:47 -0400	[thread overview]
Message-ID: <4523E13F.9080906@mentalrootkit.com> (raw)
In-Reply-To: <200610041213.03223.sgrubb@redhat.com>

Steve Grubb wrote:
> On Tuesday 03 October 2006 16:40, Linda Knippers wrote:
>   
>>> Dang! Why didn't I think of that! :-)
>>> Such a good idea. I will do a quick test and
>>> show Klaus and see if it all looks ok to him.
>>> Thanks!!!
>>>       
>> 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?
>>     
>
> Yes we care! And we should not do it with auditallow rules. The problem is 
> that to SE linux, EVERYTHING is an AVC. There is no separation of meaning by 
> using the message type. If an admin wants to query to see all the config 
> changes made during a range of time, using AVC's will not be considered in 
> the results.
>
>   

I don't understand - the object class and / or permissions will allow 
filtering and separating out the various types of AVC messages.

Karl


--
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.

  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
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 [this message]
  -- 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=4523E13F.9080906@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --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=sgrubb@redhat.com \
    --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.