Bug 1514975 - SELinux is preventing journalctl from 'map' accesses on the file /run/log/journal/43f6f51c1f464cf8b7c74d48e50ecf74/system.journal.
Summary: SELinux is preventing journalctl from 'map' accesses on the file /run/log/jou...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0ea6ea32dcf4b67aa4f486a0d7c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-19 19:21 UTC by Gene Snider
Modified: 2017-11-28 23:54 UTC (History)
5 users (show)

Fixed In Version: selinux-policy-3.13.1-283.17.fc27
Clone Of:
Environment:
Last Closed: 2017-11-28 23:54:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gene Snider 2017-11-19 19:21:40 UTC
Description of problem:
SELinux is preventing journalctl from 'map' accesses on the file /run/log/journal/43f6f51c1f464cf8b7c74d48e50ecf74/system.journal.

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

If you believe that journalctl should be allowed map access on the system.journal 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 'journalctl' --raw | audit2allow -M my-journalctl
# semodule -X 300 -i my-journalctl.pp

Additional Information:
Source Context                system_u:system_r:abrt_t:s0-s0:c0.c1023
Target Context                system_u:object_r:syslogd_var_run_t:s0
Target Objects                /run/log/journal/43f6f51c1f464cf8b7c74d48e50ecf74/
                              system.journal [ file ]
Source                        journalctl
Source Path                   journalctl
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-283.14.fc27.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 4.13.13-300.fc27.x86_64 #1 SMP Wed
                              Nov 15 15:47:50 UTC 2017 x86_64 x86_64
Alert Count                   1
First Seen                    2017-11-19 11:19:28 PST
Last Seen                     2017-11-19 11:19:28 PST
Local ID                      81c81efc-00c3-4ae9-8408-0f374b333c50

Raw Audit Messages
type=AVC msg=audit(1511119168.950:276): avc:  denied  { map } for  pid=4530 comm="journalctl" path="/run/log/journal/43f6f51c1f464cf8b7c74d48e50ecf74/system.journal" dev="tmpfs" ino=3257 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:syslogd_var_run_t:s0 tclass=file permissive=1


Hash: journalctl,abrt_t,syslogd_var_run_t,file,map

Version-Release number of selected component:
selinux-policy-3.13.1-283.14.fc27.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.13.13-300.fc27.x86_64
type:           libreport

Comment 1 Fedora Update System 2017-11-22 08:55:47 UTC
selinux-policy-3.13.1-283.17.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d05b1a2ab9

Comment 2 Fedora Update System 2017-11-22 21:41:40 UTC
selinux-policy-3.13.1-283.17.fc27 has been pushed to the Fedora 27 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-d05b1a2ab9

Comment 3 Fedora Update System 2017-11-28 23:54:05 UTC
selinux-policy-3.13.1-283.17.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.


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