From: Chris PeBenito <pebenito@ieee.org>
To: Russell Coker <russell@coker.com.au>, selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] base chrome/chromium patch
Date: Wed, 13 Jan 2021 08:51:19 -0500 [thread overview]
Message-ID: <7fd4bb68-37bf-7b1d-0527-bf515685c7c7@ieee.org> (raw)
In-Reply-To: <X/114hdXlO+f4u3Q@xev>
On 1/12/21 5:11 AM, Russell Coker wrote:
> This patch is the one I described as "another chromium patch" on the 10th of
> April last year, but with the issues addressed.
>
> I believe it's ready for inclusion.
>
>
> Signed-off-by: Russell Coker <russell@coker.com.au>
>
> Chromium policy tweaks and DRI policy
[...]
> --- refpolicy-2.20201210.orig/policy/modules/apps/chromium.if
> +++ refpolicy-2.20201210/policy/modules/apps/chromium.if
> @@ -38,7 +38,15 @@ interface(`chromium_role',`
>
> allow $2 chromium_t:process signal_perms;
> allow $2 chromium_renderer_t:process signal_perms;
> + allow $2 chromium_sandbox_t:process signal_perms;
> allow $2 chromium_naclhelper_t:process signal_perms;
> + allow chromium_t $2:process { signull signal };
> + allow $2 chromium_t:file manage_file_perms;
I think I'm ok with the other parts, but is this a typo, manage on proc/pid entries?
--
Chris PeBenito
prev parent reply other threads:[~2021-01-13 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:11 [PATCH] base chrome/chromium patch Russell Coker
2021-01-13 13:51 ` Chris PeBenito [this message]
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=7fd4bb68-37bf-7b1d-0527-bf515685c7c7@ieee.org \
--to=pebenito@ieee.org \
--cc=russell@coker.com.au \
--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).