Hide Forgot
Description of problem: SELinux is preventing abrt-hook-ccpp from 'connectto' accesses on the unix_stream_socket /run/abrt/abrt.socket. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that abrt-hook-ccpp should be allowed connectto access on the abrt.socket unix_stream_socket 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 abrt-hook-ccpp /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:abrt_dump_oops_t:s0 Target Context system_u:system_r:kernel_t:s0 Target Objects /run/abrt/abrt.socket [ unix_stream_socket ] Source abrt-hook-ccpp Source Path abrt-hook-ccpp Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages abrt-2.7.1-1.fc23.x86_64 Policy RPM selinux-policy-3.13.1-158.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.2.8-300.fc23.x86_64 #1 SMP Tue Dec 15 16:49:06 UTC 2015 x86_64 x86_64 Alert Count 5 First Seen 2016-01-08 22:13:17 CET Last Seen 2016-01-09 20:44:11 CET Local ID 944a8059-f57e-41b4-8048-3ebac16854b3 Raw Audit Messages type=AVC msg=audit(1452368651.940:551): avc: denied { connectto } for pid=1808 comm="abrt-dump-journ" path="/run/abrt/abrt.socket" scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=unix_stream_socket permissive=1 Hash: abrt-hook-ccpp,abrt_dump_oops_t,kernel_t,unix_stream_socket,connectto Version-Release number of selected component: selinux-policy-3.13.1-158.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.8-300.fc23.x86_64 type: libreport
Any idea why abrt.socket is created by kernel_t?
(In reply to Miroslav Grepl from comment #1) > Any idea why abrt.socket is created by kernel_t? I am not a selinux guru, so I would be really glad if you cloud help me. Here is the code that creates the socket: https://github.com/abrt/abrt/blob/master/src/daemon/abrtd.c#L225 What could we possible done wrong to cause the incorrect labeling of abrt.socket?
Maybe mislabeling issue. Oliver, can you still reproduce it? Thank you.
Miroslav, I am afraid I cannot. Hopefully this is a non issue now that 24 is out.
This issue is also on F24 system.
*** Bug 1381030 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.