Bug 449032

Summary: Incorrect security policy for dnsmasq
Product: [Fedora] Fedora Reporter: Bill C. Riemers <briemers>
Component: dnsmasqAssignee: Jima <jima>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8Keywords: Reopened
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-01-09 07:49:42 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
dnsmasq te file
none
dnsmasq pp file
none
dnsmasq mod file
none
dnsmasq pp file
none
dnsmasq mod file
none
grep -i dnsmasq audit.log none

Description Bill C. Riemers 2008-05-29 22:25:34 UTC 
Description of problem:

dnsmasq won't work out of the box, because the selinux security policy is wrong.


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


How reproducible:

always

Steps to Reproduce:
1. Try starting dnsmasq with selinux in enforcing mode.
2.
3.
  
Actual results:

Many setrouble messages.

Expected results:

Should work normally.

Additional info:

I will attach the *.te files created from auditing.   In addition to building
and applying the security policies I had to manually enter the commands:

touch /var/lib/misc/dnsmasq.leases
restorecon -v ./dnsmasq.leases

this should be done when installing the dnsmasq rpm.
Comment 1 Bill C. Riemers 2008-05-29 22:29:47 UTC 
Created attachment 307143 [details]
dnsmasq te file
Comment 2 Bill C. Riemers 2008-05-29 22:30:10 UTC 
Created attachment 307144 [details]
dnsmasq pp file
Comment 3 Bill C. Riemers 2008-05-29 22:30:35 UTC 
Created attachment 307145 [details]
dnsmasq mod file
Comment 4 Bill C. Riemers 2008-05-29 22:32:11 UTC 
Created attachment 307146 [details]
dnsmasq pp file
Comment 5 Bill C. Riemers 2008-05-29 22:32:54 UTC 
Created attachment 307147 [details]
dnsmasq mod file
Comment 6 Jima 2008-05-29 22:37:11 UTC 
Actually, the selinux policy is (sort of) correct; the new home for that file
(in Fedora 9 and on) is /var/lib/dnsmasq/dnsmasq.leases.  I'm not changing the
file location within a release because the likelihood of breakage is high enough
that I don't want to change it on unsuspecting users.

This is actually a duplicate of BZ#407901.

*** This bug has been marked as a duplicate of 407901 ***
Comment 7 Bill C. Riemers 2008-05-29 22:54:39 UTC 
Hmmm.  I see bug 407901 only corrects dnsmasq.leases, and does not correct any
of the other policy errors.   So I either need to reopen 407901, so the missing
policy rules can be added, or I need to reopen this one.  I'll reopen this one,
since I explicitly list the necessary rules with attachments in this bug.

I will attach my audit log.
Comment 8 Bill C. Riemers 2008-05-29 22:56:32 UTC 
Created attachment 307150 [details]
grep -i dnsmasq audit.log
Comment 9 Bug Zapper 2008-11-26 10:48:02 UTC 
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 10 Bug Zapper 2009-01-09 07:49:42 UTC 
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.