From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 10/20] xserver: xdm chats with accounts daemon over dbus
Date: Thu, 26 Sep 2013 09:12:22 -0400 [thread overview]
Message-ID: <524432B6.3060709@tresys.com> (raw)
In-Reply-To: <1380029985-25240-1-git-send-email-dominick.grift@gmail.com>
On Tue 24 Sep 2013 09:39:45 AM EDT, Dominick Grift wrote:
> make xdm_t a dbus session bus client type so that unconfined_t can chat
> with it and acquire service on it
>
> Signed-off-by: Dominick Grift <dominick.grift@gmail.com>
> ---
> policy/modules/services/xserver.te | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/policy/modules/services/xserver.te b/policy/modules/services/xserver.te
> index 4f6d693..63298c5 100644
> --- a/policy/modules/services/xserver.te
> +++ b/policy/modules/services/xserver.te
> @@ -502,6 +502,10 @@ tunable_policy(`xdm_sysadm_login',`
> ')
>
> optional_policy(`
> + accountsd_dbus_chat(xdm_t)
> +')
I think it makes more sense for this to be nested in the optional you
added below for the dbus session bus.
> +optional_policy(`
> alsa_domtrans(xdm_t)
> ')
>
> @@ -514,6 +518,11 @@ optional_policy(`
> ')
>
> optional_policy(`
> + dbus_system_bus_client(xdm_t)
> + dbus_connect_system_bus(xdm_t)
> +')
> +
> +optional_policy(`
> # Talk to the console mouse server.
> gpm_stream_connect(xdm_t)
> gpm_setattr_gpmctl(xdm_t)
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2013-09-26 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:39 [refpolicy] [PATCH 10/20] xserver: xdm chats with accounts daemon over dbus Dominick Grift
2013-09-26 13:12 ` Christopher J. PeBenito [this message]
2013-09-26 13:16 ` Dominick Grift
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=524432B6.3060709@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.