From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Allow xserver to process keyboard events
Date: Mon, 14 Feb 2011 09:14:06 -0500 [thread overview]
Message-ID: <4D5938AE.9060202@tresys.com> (raw)
In-Reply-To: <20110206150917.GA12328@siphos.be>
On 2/6/2011 10:09 AM, Sven Vermeulen wrote:
> On an Xorg 1.9 system with evdev driver (for keyboard InputClass), the
> xserver_t domain needs to be able to read from the proper device nodes as
> well as query the udev_tbl_t directory and udev itself.
Merged.
> Signed-off-by: Sven Vermeulen<sven.vermeulen@siphos.be>
> ---
> policy/modules/services/xserver.te | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/policy/modules/services/xserver.te b/policy/modules/services/xserver.te
> index 145fc4b..33b91be 100644
> --- a/policy/modules/services/xserver.te
> +++ b/policy/modules/services/xserver.te
> @@ -610,6 +610,7 @@ allow xserver_t self:unix_dgram_socket { create_socket_perms sendto };
> allow xserver_t self:unix_stream_socket { create_stream_socket_perms connectto };
> allow xserver_t self:tcp_socket create_stream_socket_perms;
> allow xserver_t self:udp_socket create_socket_perms;
> +allow xserver_t self:netlink_kobject_uevent_socket create_socket_perms;
>
> manage_dirs_pattern(xserver_t, xserver_tmp_t, xserver_tmp_t)
> manage_files_pattern(xserver_t, xserver_tmp_t, xserver_tmp_t)
> @@ -778,6 +779,10 @@ optional_policy(`
> ')
>
> optional_policy(`
> + udev_read_db(xserver_t)
> +')
> +
> +optional_policy(`
> unconfined_domain_noaudit(xserver_t)
> unconfined_domtrans(xserver_t)
> ')
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-02-14 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 15:09 [refpolicy] [PATCH 1/1] Allow xserver to process keyboard events Sven Vermeulen
2011-02-14 14:14 ` 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=4D5938AE.9060202@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.