All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCHv2 4/6] Allow wireshark to execute bin_t
Date: Fri, 9 Sep 2011 21:48:46 +0200	[thread overview]
Message-ID: <20110909194846.GG32612@siphos.be> (raw)
In-Reply-To: <20110909194626.GC32612@siphos.be>

Wireshark needs to be able to execute applications, definitely for its
plugin support, but also to call the dumpcap utility (part of the
wireshark distribution) to be able to dump the network traffic.

Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
---
 wireshark.te |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/wireshark.te b/wireshark.te
index db06f15..2ec43c4 100644
--- a/wireshark.te
+++ b/wireshark.te
@@ -69,6 +69,7 @@ kernel_read_kernel_sysctls(wireshark_t)
 kernel_read_system_state(wireshark_t)
 kernel_read_sysctl(wireshark_t)
 
+corecmd_exec_bin(wireshark_t)
 corecmd_search_bin(wireshark_t)
 
 corenet_tcp_connect_generic_port(wireshark_t)
-- 
1.7.3.4

  parent reply	other threads:[~2011-09-09 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09 19:46 [refpolicy] [PATCHv2 0/6] Wireshark application updates Sven Vermeulen
2011-09-09 19:47 ` [refpolicy] [PATCHv2 1/6] Allow using user terminals Sven Vermeulen
2011-09-09 19:47 ` [refpolicy] [PATCHv2 2/6] Allow wireshark to use the random device Sven Vermeulen
2011-09-09 19:48 ` [refpolicy] [PATCHv2 3/6] Remove duplicate corecmd_search_bin Sven Vermeulen
2011-09-09 19:48 ` Sven Vermeulen [this message]
2011-09-09 19:49 ` [refpolicy] [PATCHv2 5/6] Dumpcap dumps the packets as packet_socket Sven Vermeulen
2011-09-09 19:49 ` [refpolicy] [PATCH 6/6] Grant wireshark read access on sysfs Sven Vermeulen
2011-09-14 13:02 ` [refpolicy] [PATCHv2 0/6] Wireshark application updates 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=20110909194846.GG32612@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.