From: Chris PeBenito <pebenito@ieee.org>
To: David Sugar <dsugar@tresys.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH 1/1 v2] Add interface udev_run_domain
Date: Fri, 9 Nov 2018 19:04:38 -0500 [thread overview]
Message-ID: <4a3d1ee9-9277-1cfd-4cf4-ce2e123a2722@ieee.org> (raw)
In-Reply-To: <20181102003607.22300-1-dsugar@tresys.com>
On 11/01/2018 08:36 PM, David Sugar wrote:
> This interface is useful when using the 'RUN' option in UDEV rules where udev will be executing a user executable to perform some action. This interface allows a domain transition to occur for the run action.
>
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> policy/modules/system/udev.if | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/policy/modules/system/udev.if b/policy/modules/system/udev.if
> index a2067895..fee55852 100644
> --- a/policy/modules/system/udev.if
> +++ b/policy/modules/system/udev.if
> @@ -36,6 +36,37 @@ interface(`udev_domtrans',`
> domtrans_pattern($1, udev_exec_t, udev_t)
> ')
>
> +########################################
> +## <summary>
> +## Allow udev to execute the specified program in
> +## the specified domain.
> +## </summary>
> +## <desc>
> +## <p>
> +## This is a interface to support the UDEV 'RUN'
> +## command. This will allow the command run by
> +## udev to be run in a domain other than udev_t.
> +## </p>
> +## </desc>
> +## <param name="domain">
> +## <summary>
> +## Domain to execute in.
> +## </summary>
> +## </param>
> +## <param name="entry_file">
> +## <summary>
> +## Domain entry point file.
> +## </summary>
> +## </param>
> +#
> +interface(`udev_run_domain',`
> + gen_require(`
> + type udev_t;
> + ')
> +
> + domtrans_pattern(udev_t,$2,$1)
> +')
Merged.
--
Chris PeBenito
prev parent reply other threads:[~2018-11-10 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 0:36 [PATCH 1/1 v2] Add interface udev_run_domain David Sugar
2018-11-10 0:04 ` 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=4a3d1ee9-9277-1cfd-4cf4-ce2e123a2722@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).