From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/5] Allow asterisk to listen on its control socket
Date: Mon, 26 Mar 2012 20:49:36 +0200 [thread overview]
Message-ID: <20120326184936.GC24792@siphos.be> (raw)
In-Reply-To: <20120326184827.GA24792@siphos.be>
Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
---
asterisk.te | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/asterisk.te b/asterisk.te
index c702879..aac5a41 100644
--- a/asterisk.te
+++ b/asterisk.te
@@ -46,7 +46,7 @@ allow asterisk_t self:process { getsched setsched signal_perms getcap setcap };
allow asterisk_t self:fifo_file rw_fifo_file_perms;
allow asterisk_t self:sem create_sem_perms;
allow asterisk_t self:shm create_shm_perms;
-allow asterisk_t self:unix_stream_socket connectto;
+allow asterisk_t self:unix_stream_socket { connectto listen accept };
allow asterisk_t self:tcp_socket create_stream_socket_perms;
allow asterisk_t self:udp_socket create_socket_perms;
--
1.7.3.4
next prev parent reply other threads:[~2012-03-26 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 18:48 [refpolicy] [PATCH 0/5] Updates for asterisk domain Sven Vermeulen
2012-03-26 18:49 ` [refpolicy] [PATCH 1/5] Allow asterisk to chown its own /var/run/asterisk directory Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:49 ` Sven Vermeulen [this message]
2012-04-20 20:37 ` [refpolicy] [PATCH 2/5] Allow asterisk to listen on its control socket Christopher J. PeBenito
2012-03-26 18:50 ` [refpolicy] [PATCH 3/5] Asterisk requires access to /dev/random too Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:50 ` [refpolicy] [PATCH 4/5] Add interfaces to manage attributes of asterisk log and pid files Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:50 ` [refpolicy] [PATCH 5/5] Allow initrc to manage asterisk log and pid file attributes Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
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=20120326184936.GC24792@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.