From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/4] Adding haveged IF definition
Date: Wed, 20 Jul 2011 17:19:49 +0200 [thread overview]
Message-ID: <20110720151949.GC18841@siphos.be> (raw)
In-Reply-To: <20110720151732.GA18841@siphos.be>
Define the administrative interface so that domains can manage the haveged
processes.
Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
---
policy/modules/services/haveged.if | 26 ++++++++++++++++++++++++++
1 files changed, 26 insertions(+), 0 deletions(-)
create mode 100644 policy/modules/services/haveged.if
diff --git a/policy/modules/services/haveged.if b/policy/modules/services/haveged.if
new file mode 100644
index 0000000..4bb8f4f
--- /dev/null
+++ b/policy/modules/services/haveged.if
@@ -0,0 +1,26 @@
+## <summary>Haveged service</summary>
+
+########################################
+## <summary>
+## Administer haveged
+## </summary>
+## <param name="domain">
+## <summary>
+## Domain allowed access.
+## </summary>
+## </param>
+## <param name="role">
+## <summary>
+## The role to be allowed to manage the haveged domain.
+## </summary>
+## </param>
+## <rolecap/>
+#
+interface(`haveged_admin',`
+ gen_require(`
+ type haveged_t;
+ ')
+
+ allow $1 haveged_t:process { ptrace signal_perms };
+ ps_process_pattern($1, haveged_t)
+')
--
1.7.3.4
next prev parent reply other threads:[~2011-07-20 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 15:17 [refpolicy] [PATCH/RFC] Haveged definition Sven Vermeulen
2011-07-20 15:19 ` [refpolicy] [PATCH 1/4] Adding haveged TE definition Sven Vermeulen
2011-07-20 15:19 ` Sven Vermeulen [this message]
2011-07-20 15:20 ` [refpolicy] [PATCH 3/4] Adding haveged FC definition Sven Vermeulen
2011-07-20 15:33 ` [refpolicy] [PATCH/RFC] Haveged definition Christopher J. PeBenito
2011-07-20 15:35 ` Sven Vermeulen
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=20110720151949.GC18841@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.