From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: auditctl se_sen & se_clr
Date: Fri, 19 May 2006 15:39:31 -0400 [thread overview]
Message-ID: <200605191539.31408.sgrubb@redhat.com> (raw)
In-Reply-To: <446E1CCD.4090805@us.ibm.com>
On Friday 19 May 2006 15:30, Michael C Thompson wrote:
> This leads me to believe either our definition of se_sen is wrong, or if
> our definition of se_sen is correct, then the implementation of se_sen
> has some bug in it.
You may need to take this discussion to the LSPP mail list where more SE Linux
folks are watching. Darryl and Dustin did that work. Might be good to ask
Darryl about this.
-Steve
next prev parent reply other threads:[~2006-05-19 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 15:07 auditctl se_sen & se_clr Michael C Thompson
2006-05-19 15:17 ` Stephen Smalley
2006-05-19 15:30 ` Michael C Thompson
2006-05-19 16:31 ` James Antill
2006-05-19 17:44 ` Michael C Thompson
2006-05-19 19:19 ` James Antill
2006-05-19 19:30 ` Michael C Thompson
2006-05-19 19:39 ` Steve Grubb [this message]
2006-05-24 14:06 ` [PATCH] fix se_sen audit filter Darrel Goeddel
2006-05-26 15:43 ` auditctl se_sen & se_clr Michael C Thompson
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=200605191539.31408.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox