From: cpebenito@tresys.com (Christopher J. PeBenito)
Date: Tue, 6 Sep 2011 14:30:47 -0400
Subject: [refpolicy] [PATCH 1/6] Allow using user terminals
In-Reply-To: <20110904112545.GB2631@siphos.be>
References: <20110904112506.GA2631@siphos.be> <20110904112545.GB2631@siphos.be>
Message-ID: <4E6666D7.1040502@tresys.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On 09/04/11 07:25, Sven Vermeulen wrote:
> In order to debug wireshark startup issues, it is important that
> wireshark, when started from a command line, is allowed to output its
> error messages.
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/apps/wireshark.te |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/policy/modules/apps/wireshark.te b/policy/modules/apps/wireshark.te
> index 8bfe97d..0106846 100644
> --- a/policy/modules/apps/wireshark.te
> +++ b/policy/modules/apps/wireshark.te
> @@ -93,6 +93,7 @@ seutil_use_newrole_fds(wireshark_t)
>  sysnet_read_config(wireshark_t)
>  
>  userdom_manage_user_home_content_files(wireshark_t)
> +userdom_use_user_terminals(wireshark_t)
>  
>  tunable_policy(`use_nfs_home_dirs',`
>  	fs_manage_nfs_dirs(wireshark_t)

Isn't wireshark an X app?  Wouldn't it only need pty access?


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