From: "George C. Wilson" <ltcgcw@us.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: redhat-lspp@redhat.com, paul.moore@hp.com,
Joy Latten <latten@austin.ibm.com>,
Linda Knippers <linda.knippers@hp.com>,
Klaus Weidner <klaus@atsec.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, 4 Oct 2006 11:39:12 -0500 [thread overview]
Message-ID: <20061004163912.GA27779@us.ibm.com> (raw)
In-Reply-To: <200610041225.28836.sgrubb@redhat.com>
On Wed, Oct 04, 2006 at 12:25:28PM -0400, Steve Grubb wrote:
> On Tuesday 03 October 2006 17:26, Klaus Weidner wrote:
> > Can ausearch handle the auditallow AVC records in the audit log correctly
> > for common fields such as auid and subject MLS label?
>
> Yes it can, but there's no way to distinguish the message's proper meaning.
> You get an AVC with granted. How do you figure out that was a configuration
> change?
>
> -Steve
>
Agree. Though the information is in the AVC records, it would be difficult for
an admin to use. Also, we don't want admins to have to change the policy just
to audit in one particular case. Joy is looking at adding hooks in the SPD add
and delete paths to fix this.
--
George Wilson <ltcgcw@us.ibm.com>
IBM Linux Technology Center
--
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:39 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 [this message]
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=20061004163912.GA27779@us.ibm.com \
--to=ltcgcw@us.ibm.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=klaus@atsec.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=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.