From: Chris PeBenito <pebenito@ieee.org>
To: "Sugar, David" <dsugar@tresys.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH] Allow map permission when reading hwdb
Date: Thu, 7 Mar 2019 18:56:01 -0500 [thread overview]
Message-ID: <3ccf4761-a63a-f8f1-c52d-73c797892f8e@ieee.org> (raw)
In-Reply-To: <20190306190618.9089-2-dsugar@tresys.com>
On 3/6/19 2:07 PM, Sugar, David wrote:
> I'm seeing a denial for udev to map /etc/udev/hwdb.bin.
> This updates the existing interface to include allowing
> to map the file.
>
> type=AVC msg=audit(1551886176.948:642): avc: denied { map } for pid=5187 comm="systemd-udevd" path="/etc/udev/hwdb.bin" dev="dm-1" ino=6509618 scontext=system_u:system_r:udev_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_hwdb_t:s0 tclass=file permissive=1
>
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> policy/modules/system/systemd.if | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/policy/modules/system/systemd.if b/policy/modules/system/systemd.if
> index 8d2bb8da..03d83dc7 100644
> --- a/policy/modules/system/systemd.if
> +++ b/policy/modules/system/systemd.if
> @@ -34,7 +34,7 @@ interface(`systemd_read_hwdb',`
> type systemd_hwdb_t;
> ')
>
> - read_files_pattern($1, systemd_hwdb_t, systemd_hwdb_t)
> + mmap_read_files_pattern($1, systemd_hwdb_t, systemd_hwdb_t)
> ')
>
> ######################################
This should be a new interface.
--
Chris PeBenito
next prev parent reply other threads:[~2019-03-08 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 19:07 [PATCH v2] Add interface udev_run Sugar, David
2019-03-06 19:07 ` [PATCH] Allow map permission when reading hwdb Sugar, David
2019-03-07 23:56 ` Chris PeBenito [this message]
2019-03-07 23:55 ` [PATCH v2] Add interface udev_run Chris PeBenito
2019-03-08 3:01 ` Sugar, David
2019-03-12 0:51 ` Chris PeBenito
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=3ccf4761-a63a-f8f1-c52d-73c797892f8e@ieee.org \
--to=pebenito@ieee.org \
--cc=dsugar@tresys.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).