From: cpebenito@tresys.com (Christopher J. PeBenito)
Date: Tue, 16 Aug 2011 15:13:55 -0400
Subject: [refpolicy] [PATCH 1/1] Nagios NRPE client should be able to
 read its own configuration file
In-Reply-To: <20110813190719.GA19039@siphos.be>
References: <20110813190719.GA19039@siphos.be>
Message-ID: <4E4AC173.8020101@tresys.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On 8/13/2011 3:07 PM, Sven Vermeulen wrote:
> Currently, the nagios nrpe_t definition has no read access to its own
> nrpe_etc_t. I suspect this to be a copy/paste problem. Since the nrpe
> configuration file is stored in /etc/nagios (nagios_etc_t), NRPE does need
> search privileges in nagios_etc_t. This is easily accomplished through
> read_files_pattern.

Merged.

> Signed-off-by: Sven Vermeulen<sven.vermeulen@siphos.be>
> ---
>   policy/modules/services/nagios.te |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/policy/modules/services/nagios.te b/policy/modules/services/nagios.te
> index bf64a4c..8c70b11 100644
> --- a/policy/modules/services/nagios.te
> +++ b/policy/modules/services/nagios.te
> @@ -187,7 +187,7 @@ allow nrpe_t self:tcp_socket create_stream_socket_perms;
>
>   domtrans_pattern(nrpe_t, nagios_checkdisk_plugin_exec_t, nagios_checkdisk_plugin_t)
>
> -read_files_pattern(nrpe_t, nagios_etc_t, nagios_etc_t)
> +read_files_pattern(nrpe_t, nagios_etc_t, nrpe_etc_t)
>   files_search_etc(nrpe_t)
>
>   manage_files_pattern(nrpe_t, nrpe_var_run_t, nrpe_var_run_t)


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