Description of problem: SELinux is preventing cp from using the 'fsetid' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that cp should have the fsetid capability 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 'cp' --raw | audit2allow -M my-cp # semodule -X 300 -i my-cp.pp Additional Information: Source Context system_u:system_r:pcp_pmie_t:s0 Target Context system_u:system_r:pcp_pmie_t:s0 Target Objects Unknown [ capability ] Source cp Source Path cp Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.2-60.fc29.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.1.16-200.fc29.x86_64 #1 SMP Wed Jul 3 16:03:17 UTC 2019 x86_64 x86_64 Alert Count 1 First Seen 2019-07-14 23:41:58 MDT Last Seen 2019-07-14 23:41:58 MDT Local ID b1bae3b4-e0a1-4b4f-a9dc-af46fbacc4e8 Raw Audit Messages type=AVC msg=audit(1563169318.627:218): avc: denied { fsetid } for pid=1865 comm="cp" capability=4 scontext=system_u:system_r:pcp_pmie_t:s0 tcontext=system_u:system_r:pcp_pmie_t:s0 tclass=capability permissive=0 Hash: cp,pcp_pmie_t,pcp_pmie_t,capability,fsetid Version-Release number of selected component: selinux-policy-3.14.2-60.fc29.noarch Additional info: component: selinux-policy reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.2.11-100.fc29.x86_64 type: libreport Potential duplicate: bug 1708082
Hi Lukas, Should this capability be added to pcp_pmie_t SELinux domain? CAP_FSETID * Don't clear set-user-ID and set-group-ID mode bits when a file is modified; * set the set-group-ID bit for a file whose GID does not match the filesystem or any of the supplementary GIDs of the calling process. Thanks, Lukas.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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.
Not sure, I'd have to defer to Nathan here.
This will have originated from the pmie_check / pmie_daily scripts that help manage pmie farm startup and logs. I see pcp_pmlogger_t already has this capability for the same reasons - I'll add it into the pmie set. Thanks Lukas's.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.