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 v2] Add interface udev_run
Date: Thu, 7 Mar 2019 18:55:54 -0500 [thread overview]
Message-ID: <ff88307d-bae7-7c9c-5ca9-25b37ac30b65@ieee.org> (raw)
In-Reply-To: <20190306190618.9089-1-dsugar@tresys.com>
On 3/6/19 2:07 PM, Sugar, David wrote:
> Altered to use roleattribute based on suggestion
>
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> policy/modules/system/udev.if | 26 ++++++++++++++++++++++++++
> policy/modules/system/udev.te | 2 ++
> 2 files changed, 28 insertions(+)
>
> diff --git a/policy/modules/system/udev.if b/policy/modules/system/udev.if
> index fee55852..90dfb17d 100644
> --- a/policy/modules/system/udev.if
> +++ b/policy/modules/system/udev.if
> @@ -36,6 +36,32 @@ interface(`udev_domtrans',`
> domtrans_pattern($1, udev_exec_t, udev_t)
> ')
>
> +########################################
> +## <summary>
> +## Execute udev in the udev domain, and
> +## allow the specified role the udev domain.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed to transition.
> +## </summary>
> +## </param>
> +## <param name="role">
> +## <summary>
> +## Role allowed access.
> +## </summary>
> +## </param>
> +## <rolecap/>
> +#
> +interface(`udev_run',`
> + gen_require(`
> + attribute_role udev_roles;
> + ')
> +
> + udev_domtrans($1)
> + roleattribute $2 udev_roles;
> +')
Why is a user be starting this?
--
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
2019-03-07 23:55 ` Chris PeBenito [this message]
2019-03-08 3:01 ` [PATCH v2] Add interface udev_run 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=ff88307d-bae7-7c9c-5ca9-25b37ac30b65@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).