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 2/4] Allow puppet to call portage
Date: Tue, 13 Sep 2011 20:21:08 +0200	[thread overview]
Message-ID: <20110913182108.GC29878@siphos.be> (raw)
In-Reply-To: <20110913181932.GA29878@siphos.be>

Puppet is a configuration management and system management tool. Part of
its job is to manage the package deployments on systems. As such, it
needs the privilege to call and transition to the various portage
domains.

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

diff --git a/puppet.te b/puppet.te
index 941f6e1..022fde7 100644
--- a/puppet.te
+++ b/puppet.te
@@ -146,6 +146,12 @@ optional_policy(`
 ')
 
 optional_policy(`
+	portage_domtrans(puppet_t)
+	portage_domtrans_fetch(puppet_t)
+	portage_domtrans_gcc_config(puppet_t)
+')
+
+optional_policy(`
 	files_rw_var_files(puppet_t)
 
 	rpm_domtrans(puppet_t)
-- 
1.7.3.4

  parent reply	other threads:[~2011-09-13 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 18:19 [refpolicy] [PATCHv2 0/4] Separate domtrans/run interfaces for portage_fetch Sven Vermeulen
2011-09-13 18:20 ` [refpolicy] [PATCHv2 1/4] " Sven Vermeulen
2011-09-13 18:21 ` Sven Vermeulen [this message]
2011-09-13 18:21 ` [refpolicy] [PATCHv2 3/4] Allow sysadm_t to call all portage related services Sven Vermeulen
2011-09-13 18:22 ` [refpolicy] [PATCHv2 4/4] Allow unconfined users to call portage features Sven Vermeulen
2011-09-14 16:50   ` Christopher J. PeBenito
2011-09-14 16:49 ` [refpolicy] [PATCHv2 0/4] Separate domtrans/run interfaces for portage_fetch 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=20110913182108.GC29878@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.