Bug 831074

Summary: SELinux is preventing snort from 'create' accesses on the netlink_socket .
Product: [Fedora] Fedora Reporter: mamii <sarrab1976>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f7f15ab7d1660dd15df873f9f0e39b7e8006104e3de518e06cc15d8d15390e8f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-30 21:51:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description mamii 2012-06-12 07:07:05 UTC
libreport version: 2.0.10
executable:     /usr/bin/python2.7
hashmarkername: setroubleshoot
kernel:         3.4.2-1.fc17.x86_64
time:           Tue 12 Jun 2012 08:06:49 AM CET

:SELinux is preventing snort from 'create' accesses on the netlink_socket .
:*****  Plugin catchall (100. confidence) suggests  ***************************
:If you believe that snort should be allowed create access on the  netlink_socket by default.
:Then you should report this as a bug.
:You can generate a local policy module to allow this access.
:allow this access for now by executing:
:# grep snort /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:Additional Information:
:Source Context                system_u:system_r:snort_t:s0
:Target Context                system_u:system_r:snort_t:s0
:Target Objects                 [ netlink_socket ]
:Source                        snort
:Source Path                   snort
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-128.fc17.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Permissive
:Host Name                     (removed)
:Platform                      Linux (removed) 3.4.2-1.fc17.x86_64 #1 SMP
:                              Sat Jun 9 19:03:08 UTC 2012 x86_64 x86_64
:Alert Count                   1
:First Seen                    Tue 12 Jun 2012 08:05:54 AM CET
:Last Seen                     Tue 12 Jun 2012 08:05:54 AM CET
:Local ID                      47071570-5695-49ac-baa8-f3da0eeab652
:Raw Audit Messages
:type=AVC msg=audit(1339484754.474:56): avc:  denied  { create } for  pid=1156 comm="snort" scontext=system_u:system_r:snort_t:s0 tcontext=system_u:system_r:snort_t:s0 tclass=netlink_socket
:Hash: snort,snort_t,snort_t,netlink_socket,create
:audit2allowunable to open /sys/fs/selinux/policy:  Permission denied
:audit2allow -Runable to open /sys/fs/selinux/policy:  Permission denied

Comment 1 Miroslav Grepl 2012-06-12 10:09:32 UTC
Could you please execute

# semanage permissive -a snort_t

which will make snort_t domain as permissive and re-test it and then execute

# ausearch -m avc -ts recent

which will get us AVC msgs. Thank you.

Comment 2 Miroslav Grepl 2012-06-22 08:36:37 UTC
Fixed in selinux-policy-3.10.0-133.fc17

Comment 3 Fedora Update System 2012-06-26 21:47:34 UTC
selinux-policy-3.10.0-134.fc17 has been submitted as an update for Fedora 17.

Comment 4 Fedora Update System 2012-06-28 03:37:23 UTC
Package selinux-policy-3.10.0-134.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-134.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-06-30 21:51:20 UTC
selinux-policy-3.10.0-134.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.