SELinux is preventing /usr/sbin/dnsmasq from 'search' accesses on the directory /home.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that dnsmasq should be allowed search access on the home directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep dnsmasq /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:system_r:dnsmasq_t:s0
Target Context                system_u:object_r:home_root_t:s0
Target Objects                /home [ dir ]
Source                        dnsmasq
Source Path                   /usr/sbin/dnsmasq
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           dnsmasq-2.52-1.fc13
Target RPM Packages           filesystem-2.4.35-1.fc14
Policy RPM                    selinux-policy-3.9.7-44.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.35.14-97.fc14.x86_64 #1
                              SMP Sat Sep 17 00:15:37 UTC 2011 x86_64 x86_64
Alert Count                   3
First Seen                    Tue 25 Oct 2011 03:28:55 AM MDT
Last Seen                     Tue 25 Oct 2011 04:09:31 AM MDT
Local ID                      7a108d32-495d-40d6-9a92-f8dcea95daed

Raw Audit Messages
type=AVC msg=audit(1319537371.754:168): avc:  denied  { search } for  pid=4994 comm="dnsmasq" name="home" dev=sda1 ino=393217 scontext=unconfined_u:system_r:dnsmasq_t:s0 tcontext=system_u:object_r:home_root_t:s0 tclass=dir


type=SYSCALL msg=audit(1319537371.754:168): arch=x86_64 syscall=stat success=no exit=EACCES a0=7fff4d290a30 a1=7fff4d290af0 a2=7fff4d290af0 a3=ffffffff items=0 ppid=4993 pid=4994 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm=dnsmasq exe=/usr/sbin/dnsmasq subj=unconfined_u:system_r:dnsmasq_t:s0 key=(null)

Hash: dnsmasq,dnsmasq_t,home_root_t,dir,search

audit2allow

#============= dnsmasq_t ==============
allow dnsmasq_t home_root_t:dir search;

audit2allow -R

#============= dnsmasq_t ==============
allow dnsmasq_t home_root_t:dir search;

---SNIP---

I can't see any reasons why dnsmasq should need access to the /home directory. I've looked through its configuration file and documentation extensively and there is no mention of why it needs to do this. There have been no similar reports of this on the internet and so it looks like a peculiarity of dnsmasq and Fedora 14.