Bug 1160727

Summary: Set correct file label for start-puppet-ca wrapper script
Product: Red Hat Enterprise Linux 7 Reporter: Lukas Zapletal <lzap>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: lvrabec, lzap, mgrepl, mmalik, plautrba, pvrabec
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-10.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 10:46:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1131398    
Bug Blocks:    

Description Lukas Zapletal 2014-11-05 13:55:56 UTC 
Hello,

puppet in EPEL7 was updated and new wrapper /usr/bin/start-puppet-ca was introduced. It currently has bin_t and puppetca_exec_t is excpected:

[root@seven ~]# ll -Z /usr/bin/start-puppet-master
-rwxr-xr-x. root root system_u:object_r:puppetmaster_exec_t:s0 /usr/bin/start-puppet-master

[root@seven ~]# ll -Z /usr/bin/start-puppet-ca
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/start-puppet-ca

We need to start puppetca in its correct domain, currently this is no longer possible with EPEL7 puppet where startup wrappers were renamed.
Comment 2 Miroslav Grepl 2014-11-06 14:13:15 UTC 
Lukas,
do we still need to do these changes?
Comment 3 Lukas Zapletal 2014-11-10 14:05:52 UTC 
Yes, for both RHEL6 and RHEL7. There is no way of using the policy with EPEL puppets. See the dependant bugs. I will test your builds. Thanks!
Comment 4 Miroslav Grepl 2014-11-18 14:01:06 UTC 
commit 41f99b804d0f353916b9c22edd44518d1004432b
Author: Miroslav Grepl <mgrepl>
Date:   Tue Nov 18 15:00:43 2014 +0100

    Add support for /usr/bin/start-puppet-ca helper script.
Comment 8 errata-xmlrpc 2015-03-05 10:46:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0458.html