All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig.Grube@cobham.com (Craig Grube)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] puppet.patch - updated
Date: Fri, 04 Sep 2009 08:24:16 -0400	[thread overview]
Message-ID: <4AA106F0.9000603@cobham.com> (raw)

Attached is a new version of a patch adding support for Puppet.  The 
patch addresses most of the specific comments from Dominick Grift and 
some additional modifications.

To provide some context for the patch, which I obviously failed to do 
last week, earlier this year I started looking into using configuration 
management systems to manage SELinux clients. As far as I could tell 
everyone managing SELinux clients with Puppet are doing so with the 
client and server services running unconfined.  It seemed a bit strange 
that one would manage the configuration of clients, especially SELinux's 
configuration, using unconfined services.  The patch is an attempt to 
provide an alternative.

Running puppetmaster in it's own domain is fairly simple as it needs to 
read configuration files, manage some state, and communicate with 
clients.  Puppet's client was a bit more difficult, one option was to 
run the client unconfined due to the amount of privilege required to 
manage a system's configuration (add/remove packages, add/remove users, 
update configuration files, restart services, etc), and the other was to 
make an attempt to run the client in a separate domain with a broad but 
not complete set of privileges.  The client policy in the patch does a 
bit of both by confining puppet to its own domain and optionally calling 
unconfined_domain at the end.

The majority of testing was performed with the unconfined module not 
loaded, so my expectation is that puppet should work normally whether 
confined or not.

Here's a short summary of the files modified in the patch with a 
one-liner about changes:

services/puppet.* - new policy for Puppet client daemon

services/puppetmaster.* - new policy for Puppet server daemon

system/libraries.te, admin/usermanage.te  - allows redirection of 
standard output from ldconfig / groupadd to Puppet temp files.

system/init.if - new interface allowing transition to init script domain 
for all labeled init script types (lets Puppet restart system services 
in the proper domains)

kernel/corenetwork.te.in - adds puppet network port

If additional changes are desired or the patch should be broken up, let 
me know and I will make them.

-- 
Craig Grube

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: puppet.patch
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20090904/3c31ff56/attachment.ksh 

             reply	other threads:[~2009-09-04 12:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 12:24 Craig Grube [this message]
2009-09-04 13:53 ` [refpolicy] puppet.patch - updated Dominick Grift
2009-09-04 14:13 ` Dominick Grift
2009-09-05  9:01 ` Dominick Grift
2009-09-05  9:38 ` Dominick Grift
2009-09-06 16:15   ` Craig Grube
2009-09-06 16:23     ` Dominick Grift
2009-09-07 18:39       ` Craig Grube
2009-09-08 10:28         ` Dominick Grift
2009-09-08 23:23           ` Craig Grube
2009-09-09  9:07             ` Dominick Grift
2009-09-10 11:14               ` Craig Grube

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=4AA106F0.9000603@cobham.com \
    --to=craig.grube@cobham.com \
    --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.