From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Mount output should be writeable to puppet_tmp_t
Date: Sat, 24 Sep 2011 15:56:58 +0200 [thread overview]
Message-ID: <20110924135657.GA8045@siphos.be> (raw)
When using puppet to configure systems, the puppet system
runs the mount command and captures its output in a temporary
file in /tmp (which is labeled puppet_tmp_t).
Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
---
policy/modules/system/mount.te | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/policy/modules/system/mount.te b/policy/modules/system/mount.te
index 1284081..ca9cdc0 100644
--- a/policy/modules/system/mount.te
+++ b/policy/modules/system/mount.te
@@ -191,6 +191,10 @@ optional_policy(`
')
')
+optional_policy(`
+ puppet_rw_tmp(mount_t)
+')
+
# for kernel package installation
optional_policy(`
rpm_rw_pipes(mount_t)
--
1.7.3.4
next reply other threads:[~2011-09-24 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 13:56 Sven Vermeulen [this message]
2011-09-24 15:18 ` [refpolicy] [PATCH 1/1] Mount output should be writeable to puppet_tmp_t Dominick Grift
2011-09-24 15:22 ` Dominick Grift
2011-09-26 13:12 ` Daniel J Walsh
2011-09-26 14:22 ` Sven Vermeulen
2011-09-26 15:01 ` Daniel J Walsh
2011-09-26 15:11 ` Dominick Grift
2011-09-26 15:41 ` Daniel J Walsh
2011-09-26 18:31 ` Christopher J. PeBenito
2011-09-26 19:36 ` Matt Thode
2011-09-27 12:59 ` Daniel J Walsh
2011-09-27 13:17 ` Matt Thode
2011-09-27 13:29 ` Christopher J. PeBenito
2011-09-27 14:58 ` Daniel J Walsh
2011-09-27 15:57 ` Christopher J. PeBenito
2011-09-27 16:37 ` Dominick Grift
2011-09-27 18:06 ` Daniel J Walsh
2011-09-27 16:40 ` Sven Vermeulen
2011-09-27 18:03 ` Daniel J Walsh
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=20110924135657.GA8045@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.