Description of problem: I did execute the " restorecon -Rv /" to fix lables on my system but still this issue is ocurring SELinux is preventing (coredump) from 'remount' accesses on the filesystem . ***** Plugin catchall (100. confidence) suggests ************************** If you believe that (coredump) should be allowed remount access on the filesystem 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 '(coredump)' --raw | audit2allow -M my-coredump # semodule -X 300 -i my-coredump.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:unlabeled_t:s0 Target Objects [ filesystem ] Source (coredump) Source Path (coredump) Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.1-13.fc28.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.16.0-0.rc5.git0.1.fc28.x86_64 #1 SMP Mon Mar 12 20:10:40 UTC 2018 x86_64 x86_64 Alert Count 122 First Seen 2018-03-08 09:19:57 IST Last Seen 2018-03-14 08:38:55 IST Local ID a2c963ae-809b-4190-a8bd-2b28d2c32e09 Raw Audit Messages type=AVC msg=audit(1520996935.724:308): avc: denied { remount } for pid=3509 comm="(-localed)" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=0 Hash: (coredump),init_t,unlabeled_t,filesystem,remount Version-Release number of selected component: selinux-policy-3.14.1-13.fc28.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.16.0-0.rc5.git0.1.fc28.x86_64 type: libreport Potential duplicate: bug 1554000
Is there any way to self-access and find that I need to run "restorecon -Rv /"? Is it not possible to create any legitimate policy for such coredump issues?
This is just not stopping, I have executed this exact command sudo restorecon -Rv / still getting notifications.
Description of problem: When a program (any program) crashes and dumps core, this alert pops up. Easy way to reproduce: sleep 10 hit control-backslash to send a SIGQUIT to the sleep. Version-Release number of selected component: selinux-policy-3.14.1-11.fc28.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.16.0-0.rc4.git0.1.fc28.x86_64 type: libreport
*** Bug 1554462 has been marked as a duplicate of this bug. ***
Description of problem: Popped up after launching gnome-boxes Version-Release number of selected component: selinux-policy-3.14.1-13.fc28.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.16.0-0.rc5.git0.1.fc28.x86_64 type: libreport
Description of problem: Doing nothing (was away from pc) Version-Release number of selected component: selinux-policy-3.14.1-13.fc28.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.16.0-0.rc5.git0.1.fc28.x86_64 type: libreport
selinux-policy-3.14.1-17.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b8cb71b345
selinux-policy-3.14.1-17.fc28 has been pushed to the Fedora 28 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-2018-b8cb71b345
selinux-policy-3.14.1-18.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7821b2e7c4
selinux-policy-3.14.1-18.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.