Description of problem: I find avc messages for spacewalk abrt on Fedora 22 ---- time->Sun Sep 13 19:39:51 2015 type=AVC msg=audit(1442187591.812:1655): avc: denied { execmem } for pid=30860 comm="spacewalk-abrt" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=process permissive=0 ---- time->Sun Sep 13 19:39:53 2015 type=AVC msg=audit(1442187593.915:1657): avc: denied { sigchld } for pid=30869 comm="abrt-hook-ccpp" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0 ---- time->Sun Sep 13 19:40:05 2015 type=AVC msg=audit(1442187605.891:1658): avc: denied { execmem } for pid=31022 comm="spacewalk-abrt" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=process permissive=0 Version-Release number of selected component (if applicable): spacewalk-selinux-2.3.2-1.fc22.noarch How reproducible: always on fedora 22
Following local policy solved the problem. SELinux denials and segfaults do not appear anymore. # cat mypolicy.te policy_module(mypolicy, 1.0) require { type abrt_t; type kernel_t; class process { execmem sigchld }; } allow abrt_t abrt_t : process { execmem }; allow abrt_t kernel_t : process { sigchld }; #
Problem with selinux still exists on Fedora 24 time->Thu Oct 6 19:01:26 2016 type=AVC msg=audit(1475794886.859:821): avc: denied { write } for pid=2789 comm="spacewalk-abrt" name="spacewalk_abrt" dev="dm-0" ino=9068401 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir permissive=0 ---- time->Thu Oct 6 19:01:26 2016 type=AVC msg=audit(1475794886.869:822): avc: denied { execmem } for pid=2789 comm="spacewalk-abrt" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=process permissive=0 ---- package: selinux-policy-3.13.1-191.17.fc24.noarch
Pavel, do you see these selinux denials on the Spacewalk server or on the client system registered to Spacewalk?
We still see this problem in our automation on Fedora 24. time->Mon Jan 30 12:44:54 2017 type=AVC msg=audit(1485798294.573:1032): avc: denied { execmem } for pid=9475 comm="spacewalk-abrt" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=process permissive=0
*** Bug 1398376 has been marked as a duplicate of this bug. ***
Problem is only on client side with spacewalk-abrt. Reproducer from Bug 1398376 Steps to Reproduce: 0. install spacewalk-abrt 1. abrt-auto-reporting enabled 2. run abrt service - systemctl restart abrt-oops abrt-ccpp abrtd 3. produce event for abrt (kill -s SEGV)
Same AVC message on Fedora 25 - only client side. type=AVC msg=audit(1485870209.555:188): avc: denied { execmem } for pid=3609 comm="spacewalk-abrt" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=process permissive=0
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.