selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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] Add interface to run cdrecord in caller domain
Date: Tue, 19 Feb 2019 19:31:56 -0800	[thread overview]
Message-ID: <076c9f96f58d7e7e022dff3d9d8476650f8d7b1d.camel@ieee.org> (raw)
In-Reply-To: <20190218200017.4439-2-dsugar@tresys.com>

On Mon, 2019-02-18 at 20:00 +0000, Sugar, David wrote:
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
>  policy/modules/apps/cdrecord.if | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/policy/modules/apps/cdrecord.if
> b/policy/modules/apps/cdrecord.if
> index fbc20f69..ba81fb1a 100644
> --- a/policy/modules/apps/cdrecord.if
> +++ b/policy/modules/apps/cdrecord.if
> @@ -30,3 +30,22 @@ interface(`cdrecord_role',`
>  	allow $2 cdrecord_t:process { ptrace signal_perms };
>  	ps_process_pattern($2, cdrecord_t)
>  ')
> +
> +########################################
> +## <summary>
> +##	Execute cdrecord in the caller domain.
> +## </summary>
> +## <param name="domain">
> +##	<summary>
> +##	Domain allowed access.
> +##	</summary>
> +## </param>
> +#
> +interface(`cdrecord_exec',`
> +	gen_require(`
> +		type cdrecord_exec_t;
> +	')
> +
> +	corecmd_search_bin($1)
> +	can_exec($1, cdrecord_exec_t)
> +')

Merged.

-- 
Chris PeBenito



  reply	other threads:[~2019-02-20  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 20:00 [PATCH] Add interface to get status of rsyslog service Sugar, David
2019-02-18 20:00 ` [PATCH] Add interface to run cdrecord in caller domain Sugar, David
2019-02-20  3:31   ` Chris PeBenito [this message]
2019-02-20  3:32 ` [PATCH] Add interface to get status of rsyslog service 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=076c9f96f58d7e7e022dff3d9d8476650f8d7b1d.camel@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).