From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Changes to the xserver policy module
Date: Fri, 19 Oct 2012 09:20:19 -0400 [thread overview]
Message-ID: <50815393.4060706@tresys.com> (raw)
In-Reply-To: <1350476918-5838-1-git-send-email-dominick.grift@gmail.com>
On 10/17/12 08:28, Dominick Grift wrote:
>
> These interfaces are needed by at least plymouth
>
> Signed-off-by: Dominick Grift <dominick.grift@gmail.com>
> diff --git a/policy/modules/services/xserver.if b/policy/modules/services/xserver.if
> index 130ced9..15abcfa 100644
> --- a/policy/modules/services/xserver.if
> +++ b/policy/modules/services/xserver.if
> @@ -713,6 +713,47 @@
>
> ########################################
> ## <summary>
> +## Create, read, write, and delete
> +## xdm_spool files.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`xserver_manage_spool_files_xdm',`
> + gen_require(`
> + type xdm_spool_t;
> + ')
> +
> + files_search_spool($1)
> + manage_files_pattern($1, xdm_spool_t, xdm_spool_t)
> +')
> +
> +########################################
> +## <summary>
> +## Read xdm process state files.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`xserver_read_state_xdm',`
> + gen_require(`
> + type xdm_t;
> + ')
> +
> + kernel_search_proc($1)
> + allow $1 xdm_t:dir list_dir_perms;
> + allow $1 xdm_t:file read_file_perms;
> + allow $1 xdm_t:lnk_file read_lnk_file_perms;
> +')
Merged. I swapped the interfaces and renamed them.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-10-19 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 12:28 [refpolicy] [PATCH] Changes to the xserver policy module Dominick Grift
2012-10-19 13:20 ` Christopher J. 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=50815393.4060706@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.