From: Paul Moore <paul@paul-moore.com>
To: Stephen Smalley <stephen.smalley@gmail.com>
Cc: selinux <selinux@tycho.nsa.gov>, linux-audit@redhat.com
Subject: Re: [RFC][PATCH] selinux: Report result in avc messages
Date: Fri, 02 May 2014 15:47:12 -0400 [thread overview]
Message-ID: <3643773.YnIcfvMkr3@sifl> (raw)
In-Reply-To: <CAB9W1A1FrGKHO8g7JrgZYO-ZYpr61A8ScgHr0tWgt0uA1_j3rA@mail.gmail.com>
On Thursday, May 01, 2014 01:11:57 PM Stephen Smalley wrote:
> I'm fine with it as is.
Okay, it's applied to the next branch.
> On Thu, May 1, 2014 at 12:09 PM, Paul Moore <paul@paul-moore.com> wrote:
> > On Wednesday, April 30, 2014 09:08:28 AM Stephen Smalley wrote:
> >> The revised patch switched from result=allowed|denied to
> >> permissive=0|1 in the avc message. I think Bill's point was with
> >> respect to the code, which still internally is passing around the
> >> result of the decision and inferring the permissive state from it,
> >> rather than the output string itself.
> >
> > I'm fine with this patch, but before I merge it for next I just wanted to
> > make sure there isn't another revision coming?
> >
> > --
> > paul moore
> > www.paul-moore.com
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2014-05-02 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB9W1A3BxZ=U=+t4o3q+EomuxK256Ou1EAqyHXrLm59PB=p7kA@mail.gmail.com>
2014-04-30 2:59 ` [RFC][PATCH] selinux: Report result in avc messages Eric Paris
2014-04-30 12:59 ` Daniel J Walsh
2014-04-30 13:29 ` Steve Grubb
2014-04-30 13:34 ` Daniel J Walsh
2014-04-30 15:18 ` Stephen Smalley
2014-04-30 15:38 ` Stephen Smalley
2014-04-30 15:48 ` William Roberts
2014-04-30 16:01 ` Steve Grubb
2014-04-30 16:08 ` Stephen Smalley
2014-04-30 16:20 ` William Roberts
2014-05-01 19:09 ` Paul Moore
2014-05-01 20:11 ` Stephen Smalley
2014-05-02 19:47 ` Paul Moore [this message]
2014-04-30 15:52 ` Eric Paris
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=3643773.YnIcfvMkr3@sifl \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=stephen.smalley@gmail.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