From: Daniel J Walsh <dwalsh@redhat.com>
To: Eric Paris <eparis@redhat.com>,
Stephen Smalley <stephen.smalley@gmail.com>
Cc: linux-audit@redhat.com, selinux <selinux@tycho.nsa.gov>
Subject: Re: [RFC][PATCH] selinux: Report result in avc messages
Date: Wed, 30 Apr 2014 08:59:50 -0400 [thread overview]
Message-ID: <5360F3C6.4090501@redhat.com> (raw)
In-Reply-To: <1398826782.10979.9.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1170 bytes --]
How about permitted rather then allowed.
On 04/29/2014 10:59 PM, Eric Paris wrote:
> On Tue, 2014-04-29 at 16:54 -0700, Stephen Smalley wrote:
>> Requested for Android in order to distinguish denials that are not in
>> fact breaking anything yet due to permissive domains versus denials
>> that are being enforced, but seems generally useful. result field was
>> already in the selinux audit data structure and was being passed to
>> avc_audit() but wasn't being used. Seems to cause no harm to ausearch
>> or audit2allow to add it as a field. Comments?
> I think it's a great idea, but I'm worried that Steve is going to get
> grumpy because an AVC record is going to have a result= field which is
> similar, but not necessarily related to the res= field of a SYSCALL
> record. Seems easily confused (although probably 9999 times out of
> 10000 they will be the same)
>
> So while I wholeheartedly think we should take the idea, I wonder if
> someone can dream up a name that isn't confusingly similar...
>
> I can't think of anything...
>
> -Eric
>
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
[-- Attachment #1.2: Type: text/html, Size: 1872 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-04-30 12:59 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 [this message]
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
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=5360F3C6.4090501@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.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