All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2] New policy for tboot utilities
Date: Mon, 7 Mar 2016 10:13:29 -0500	[thread overview]
Message-ID: <56DD9A99.1080709@tresys.com> (raw)
In-Reply-To: <1457218424-15243-1-git-send-email-aranea@aixah.de>

On 3/5/2016 5:53 PM, Luis Ressel wrote:
> tboot is an OSS project for using the features of Intel TXT. Some of its
> included utilities (might) need special permissions. For now, there's
> only a policy for txt-stat (it needs access to /dev/mem).


> +########################################
> +## <summary>
> +##	Role access for txt-stat
> +## </summary>
> +## <param name="role">
> +##	<summary>
> +##	Role allowed access
> +##	</summary>
> +## </param>
> +## <param name="domain">
> +##	<summary>
> +##	User domain for the role
> +##	</summary>
> +## </param>
> +#
> +interface(`tboot_txtstat_role',`
> +	gen_require(`
> +		type txtstat_t;
> +	')
> +
> +	tboot_run_txtstat($2, $1)
> +
> +	ps_process_pattern($2, txtstat_t)
> +	allow $2 txtstat_t:process { signull signal sigkill };
> +')

Are all of the utilities simple command line tools (the ones that may
need domains in the future)?  If so, this interface doesn't seem
necessary.  The role interfaces are usually for complicated apps that
have their own derived types e.g. for home directory content.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2016-03-07 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05 22:53 [refpolicy] [PATCH v2] New policy for tboot utilities Luis Ressel
2016-03-07 15:13 ` Christopher J. PeBenito [this message]
2016-03-07 15:18   ` Luis Ressel

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=56DD9A99.1080709@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=refpolicy@oss.tresys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.