From: sven.vermeulen@siphos.be (Sven Vermeulen) Date: Sat, 13 Aug 2011 21:07:19 +0200 Subject: [refpolicy] [PATCH 1/1] Nagios NRPE client should be able to read its own configuration file Message-ID: <20110813190719.GA19039@siphos.be> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com 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. Signed-off-by: Sven Vermeulen --- 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) -- 1.7.3.4