Bug 622448

Summary: incorrect label on boinc client init script
Product: Red Hat Enterprise Linux 6 Reporter: Milos Malik <mmalik>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED CURRENTRELEASE QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: dwalsh, mgrepl
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: selinux-policy-3.7.19-37.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:36:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Milos Malik 2010-08-09 12:07:33 UTC
Description of problem:
boinc-client package (which is available from RHEL-6 EPEL repo) contains an init script with '-' in its name, but selinux-policy expects '_' in the name.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
# ls -Z /etc/rc.d/init.d/boinc-client 
-rwxr-xr-x. root root system_u:object_r:initrc_exec_t:s0 /etc/rc.d/init.d/boinc-client
# ls -Z /etc/rc.d/init.d/boinc_client 
ls: cannot access /etc/rc.d/init.d/boinc_client: No such file or directory
# matchpathcon /etc/rc.d/init.d/boinc-client
/etc/rc.d/init.d/boinc-client   system_u:object_r:initrc_exec_t:s0
# matchpathcon /etc/rc.d/init.d/boinc_client
/etc/rc.d/init.d/boinc_client   system_u:object_r:boinc_initrc_exec_t:s0

Actual results:
the init script is labelled incorrectly

Expected results:
the init script is labelled correctly

Comment 1 Miroslav Grepl 2010-08-09 12:46:20 UTC
I am fixing the label to

/etc/rc\.d/init\.d/boinc-client     --  gen_context(system_u:object_r:boinc_initrc_exec_t,s0)

Comment 2 Miroslav Grepl 2010-08-10 18:13:14 UTC
Fixed in selinux-policy-3.7.19-37.el6.noarch

Comment 4 releng-rhel@redhat.com 2010-11-10 21:36:05 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.