Bug 1460884 - SELinux is preventing systemd-tmpfile from using the dac_read_search capability
Summary: SELinux is preventing systemd-tmpfile from using the dac_read_search capability
Keywords:
Status: CLOSED DUPLICATE of bug 1460882
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-13 03:27 UTC by Chris Murphy
Modified: 2017-06-13 12:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-13 12:53:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal (575.88 KB, text/x-vhdl)
2017-06-13 03:27 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2017-06-13 03:27:01 UTC
Created attachment 1287142 [details]
journal

Description of problem:

SETroubleshoot notification at login appears, with this complaint.


Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-254.fc26.noarch
4.12.0-0.rc5.git0.1.fc27.x86_64


How reproducible:
Each boot.


Steps to Reproduce:
1. Boot
2.
3.

Actual results:

SELinux alert notification

Raw Audit Messages
type=AVC msg=audit(1497324182.855:372): avc:  denied  { dac_read_search } for  pid=2758 comm="systemd-tmpfile" capability=2  scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:system_r:systemd_tmpfiles_t:s0 tclass=capability permissive=0


Expected results:

No notification for just booting and logging in.


Additional info:

Could be related to upgrading the kernel from 4.11.3 to 4.12rc5; I don't recall these SELinux alerts happening prior to the upgrade.

Comment 1 Chris Murphy 2017-06-13 03:54:48 UTC
Also happens with selinux-policy-3.13.1-257.fc26.noarch and manually relabelled.

Comment 2 Lukas Vrabec 2017-06-13 12:53:12 UTC

*** This bug has been marked as a duplicate of bug 1460882 ***


Note You need to log in before you can comment on or make changes to this bug.