Bug 494370

Summary: bind init script references obsolete SELinux's booleans and points to wrong booleans.local location
Product: Red Hat Enterprise Linux 5 Reporter: Mauricio Silveira <mauricio>
Component: bindAssignee: Adam Tkac <atkac>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: ovasik, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 07:38:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fix path for booleans.local none

Description Mauricio Silveira 2009-04-06 15:41:40 UTC
Created attachment 338351 [details]
Fix path for booleans.local

Description of problem:
bind init script /etc/init.d/named has deprecated references to SELinux booleans and wrong reference location to booleans.local

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

How reproducible: 
Always

Actual results:
/etc/selinux/${SELINUXTYPE}/modules/active/booleans should not be used at all.
Script points to /etc/selinux/${SELINUXTYPE}/booleans.local when the path should be /etc/selinux/${SELINUXTYPE}/modules/active/booleans

Expected results:
Do no try to access /etc/selinux/${SELINUXTYPE}{/,/modules/active}/booleans at all.
Point to /etc/selinux/${SELINUXTYPE}/modules/active/booleans.local instead of /etc/selinux/${SELINUXTYPE}/booleans.local

Additional info:
Patch included

Comment 1 Adam Tkac 2009-04-08 10:42:24 UTC
Both solutions are broken by design, the best solution is to use "getsebool" utility.

Comment 6 errata-xmlrpc 2009-09-02 07:38:00 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1420.html