From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: [PATCH V2] libselinux: Add permissive= entry to avc audit log
Date: Fri, 28 Apr 2017 15:10:21 +0200 [thread overview]
Message-ID: <20170428131021.GA13764@julius> (raw)
In-Reply-To: <20170428130516.4021-1-richard_c_haines@btinternet.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Fri, Apr 28, 2017 at 02:05:16PM +0100, Richard Haines wrote:
> Add audit log entry to specify whether the decision was made in
> permissive mode/permissive domain or enforcing mode.
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
> V2 changes: Remove utilities and follow the kernel way of detecting
> whether permissive or not.
>
> libselinux/src/avc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/libselinux/src/avc.c b/libselinux/src/avc.c
> index b1ec57f..96b2678 100644
> --- a/libselinux/src/avc.c
> +++ b/libselinux/src/avc.c
> @@ -723,6 +723,10 @@ void avc_audit(security_id_t ssid, security_id_t tsid,
>
> log_append(avc_audit_buf, " ");
> avc_dump_query(ssid, tsid, tclass);
> +
> + if (denied)
> + log_append(avc_audit_buf, " permissive=%u", result ? 0 : 1);
> +
> log_append(avc_audit_buf, "\n");
> avc_log(SELINUX_AVC, "%s", avc_audit_buf);
>
> --
> 2.9.3
>
I hope you will still submit the utils as well. I think/hope that the selinux_check_access util can be used with shell scripts to create a simple user space object manager example
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2017-04-28 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 13:05 [PATCH V2] libselinux: Add permissive= entry to avc audit log Richard Haines
2017-04-28 13:10 ` Dominick Grift [this message]
2017-04-28 13:22 ` Richard Haines
2017-04-28 14:52 ` Stephen Smalley
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=20170428131021.GA13764@julius \
--to=dac.override@gmail.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.