Bug 1429164

Summary: SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file nss.
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: awilliam, bugzilla, dominick.grift, dwalsh, gmarr, lvrabec, mgrepl, plautrba, pmoore, robatino, sgallagh, ssekidde, znmeb
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:312dbf3be6dc1d1fbaef92eb2990b06e2dc649ec4e018258ab068cce2860fa4f;VARIANT_ID=workstation; AcceptedBlocker
Fixed In Version: selinux-policy-3.13.1-246.fc26 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 02:40:35 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:
Bug Depends On:    
Bug Blocks: 1349188    

Description Joachim Frieben 2017-03-05 08:10:09 UTC
Description of problem:
SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file nss.

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

If you believe that abrt-dump-journ should be allowed write access on the nss sock_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:
# ausearch -c 'abrt-dump-journ' --raw | audit2allow -M my-abrtdumpjourn
# semodule -X 300 -i my-abrtdumpjourn.pp

Additional Information:
Source Context                system_u:system_r:abrt_dump_oops_t:s0
Target Context                system_u:object_r:sssd_var_lib_t:s0
Target Objects                nss [ sock_file ]
Source                        abrt-dump-journ
Source Path                   abrt-dump-journ
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-241.fc26.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.11.0-0.rc0.git9.1.fc26.x86_64 #1
                              SMP Fri Mar 3 16:57:16 UTC 2017 x86_64 x86_64
Alert Count                   2
First Seen                    2017-03-05 09:06:51 CET
Last Seen                     2017-03-05 09:08:29 CET
Local ID                      c44fb896-3493-4115-b048-a25f7bd841b5

Raw Audit Messages
type=AVC msg=audit(1488701309.259:338): avc:  denied  { write } for  pid=773 comm="abrt-dump-journ" name="nss" dev="dm-2" ino=1968 scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:object_r:sssd_var_lib_t:s0 tclass=sock_file permissive=0


Hash: abrt-dump-journ,abrt_dump_oops_t,sssd_var_lib_t,sock_file,write

Version-Release number of selected component:
selinux-policy-3.13.1-241.fc26.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.0
hashmarkername: setroubleshoot
kernel:         4.11.0-0.rc0.git9.1.fc26.x86_64
type:           libreport

Comment 1 Adam Williamson 2017-03-13 23:31:31 UTC
Description of problem:
Happens on boot of a freshly installed Fedora 26 Workstation system.

Version-Release number of selected component:
selinux-policy-3.13.1-244.fc26.noarch

Additional info:
reporter:       libreport-2.9.0
hashmarkername: setroubleshoot
kernel:         4.11.0-0.rc1.git0.1.fc26.x86_64
type:           libreport

Comment 2 Adam Williamson 2017-03-13 23:32:07 UTC
Nominating as a Final blocker: this seems like a violation of "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop" - https://fedoraproject.org/wiki/Fedora_26_Final_Release_Criteria#SELinux_and_crash_notifications

Comment 3 M. Edward (Ed) Borasky 2017-03-17 03:09:26 UTC
Description of problem:
Booting the F26 Alpha Live workstation test compose

Version-Release number of selected component:
selinux-policy-3.13.1-244.fc26.noarch

Additional info:
reporter:       libreport-2.9.0
hashmarkername: setroubleshoot
kernel:         4.11.0-0.rc2.git2.2.fc26.x86_64
type:           libreport

Comment 4 Fedora Update System 2017-03-17 22:48:27 UTC
selinux-policy-3.13.1-245.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-58233b1a16

Comment 5 Fedora Update System 2017-03-19 14:21:52 UTC
selinux-policy-3.13.1-246.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-58233b1a16

Comment 6 Geoffrey Marr 2017-03-20 21:06:44 UTC
Discussed during the 2017-03-20 blocker review meeting: [1]

The decision was made to classify this bug as an AcceptedBlocker (Final) as it violates the following criteria:

"There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-03-20/f26-blocker-review.2017-03-20-16.06.txt

Comment 7 Fedora Update System 2017-03-21 02:40:35 UTC
selinux-policy-3.13.1-246.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.