From: sven.vermeulen@siphos.be (Sven Vermeulen) Date: Fri, 19 Oct 2012 20:53:55 +0200 Subject: [refpolicy] [PATCH 2/7] Fix startup issue with fail2ban-client In-Reply-To: <1350672840-14590-1-git-send-email-sven.vermeulen@siphos.be> References: <1350672840-14590-1-git-send-email-sven.vermeulen@siphos.be> Message-ID: <1350672840-14590-3-git-send-email-sven.vermeulen@siphos.be> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com The fail2ban-client application fails to start if it isn't allowed to create, connect, read and write to its own unix_stream_socket. Signed-off-by: Sven Vermeulen --- fail2ban.te | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/fail2ban.te b/fail2ban.te index bd529c0..ed39236 100644 --- a/fail2ban.te +++ b/fail2ban.te @@ -124,6 +124,8 @@ optional_policy(` # Client Local policy # +allow fail2ban_client_t self:unix_stream_socket { create connect write read }; + domtrans_pattern(fail2ban_client_t, fail2ban_exec_t, fail2ban_t) stream_connect_pattern(fail2ban_client_t, fail2ban_var_run_t, fail2ban_var_run_t, fail2ban_t) -- 1.7.8.6