From: Paul Moore <paul@paul-moore.com>
To: selinux@tycho.nsa.gov
Cc: linux-audit@redhat.com
Subject: Re: [RFC][PATCH] selinux: Report result in avc messages
Date: Thu, 01 May 2014 15:09:43 -0400 [thread overview]
Message-ID: <4012781.FYeZg7nLGc@sifl> (raw)
In-Reply-To: <CAB9W1A3-juzF1Ze3uDhtnMdOtMQtOgaG3+z_3vWYQ3TmcJK0=A@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul@paul-moore.com>
To: selinux@tycho.nsa.gov
Cc: Steve Grubb <sgrubb@redhat.com>, linux-audit@redhat.com
Subject: Re: [RFC][PATCH] selinux: Report result in avc messages
Date: Thu, 01 May 2014 15:09:43 -0400 [thread overview]
Message-ID: <4012781.FYeZg7nLGc@sifl> (raw)
In-Reply-To: <CAB9W1A3-juzF1Ze3uDhtnMdOtMQtOgaG3+z_3vWYQ3TmcJK0=A@mail.gmail.com>
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
next prev parent reply other threads:[~2014-05-01 19:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 23:54 [RFC][PATCH] selinux: Report result in avc messages Stephen Smalley
2014-04-30 0:22 ` William Roberts
2014-04-30 2:59 ` Eric Paris
2014-04-30 2:59 ` Eric Paris
2014-04-30 12:59 ` Daniel J Walsh
2014-04-30 12:59 ` Daniel J Walsh
2014-04-30 13:29 ` Steve Grubb
2014-04-30 13:29 ` Steve Grubb
2014-04-30 13:34 ` Daniel J Walsh
2014-04-30 13:34 ` Daniel J Walsh
2014-04-30 15:18 ` Stephen Smalley
2014-04-30 15:18 ` Stephen Smalley
2014-04-30 15:38 ` Stephen Smalley
2014-04-30 15:38 ` Stephen Smalley
2014-04-30 15:48 ` William Roberts
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-04-30 16:20 ` William Roberts
2014-05-01 19:09 ` Paul Moore [this message]
2014-05-01 19:09 ` Paul Moore
2014-05-01 20:11 ` Stephen Smalley
2014-05-01 20:11 ` Stephen Smalley
2014-05-02 19:47 ` Paul Moore
2014-05-02 19:47 ` Paul Moore
2014-04-30 15:52 ` Eric Paris
2014-04-30 15:52 ` Eric Paris
2014-04-30 12:56 ` 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=4012781.FYeZg7nLGc@sifl \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.