Description of problem:  Dump provided by Details button.  Report Bug button not functioning:

SELinux is preventing /usr/bin/boinc_client from read access on the file /etc/hosts.

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

If you believe that boinc_client should be allowed read access on the hosts file 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 boinc_client /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:boinc_t:s0
Target Context                system_u:object_r:net_conf_t:s0
Target Objects                /etc/hosts [ file ]
Source                        boinc_client
Source Path                   /usr/bin/boinc_client
Port                          <Unknown>
Host                          homenet06.homenet
Source RPM Packages           boinc-client-6.12.35-1.r24014svn.fc16
Target RPM Packages           setup-2.8.36-2.fc16
Policy RPM                    selinux-policy-3.10.0-67.fc16
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     homenet06.homenet
Platform                      Linux homenet06.homenet 3.1.5-2.fc16.x86_64 #1 SMP
                              Mon Dec 12 21:25:51 UTC 2011 x86_64 x86_64
Alert Count                   1
First Seen                    Fri 23 Dec 2011 11:24:00 AM CST
Last Seen                     Fri 23 Dec 2011 11:24:00 AM CST
Local ID                      c6f33d56-74c9-457e-a202-32689ca452a9

Raw Audit Messages
type=AVC msg=audit(1324661040.247:7497): avc:  denied  { read } for  pid=11638 comm="boinc_client" name="hosts" dev=dm-1 ino=1703975 scontext=system_u:system_r:boinc_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file



Version-Release number of selected component (if applicable): 3.10.0-67.fc16.noarch


How reproducible: Restarted system after an update.


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: See bug #770452