Description of problem: If webalizer is executed from crond, it tries to create some files in /var/lib/webalizer and /var/www/usage directories, but it fails because of SELinux. Because webalizer runs as root/root, SELinux complains about missing dac_override rule. Allowing dac_override permission for webalizer_t domain was not accepted by the SELinux policy maintainers, therefore I suggest a different solution. This problem can be solved by adding write permission for group on both directories: # ls -ld /var/lib/webalizer/ drwxrwxr-x. 2 webalizer root 4096 Sep 20 08:38 /var/lib/webalizer/ # ls -ld /var/www/usage/ drwxrwxr-x. 2 webalizer root 4096 Sep 20 08:38 /var/www/usage/ # After applying this change, SELinux denials do not appear anymore. Version-Release number of selected component (if applicable): webalizer-2.23_08-13.fc31.x86_64 How reproducible: * always Steps to Reproduce: * the same steps as in https://bugzilla.redhat.com/show_bug.cgi?id=1753292 Actual results: * SELinux denials which are listed in comment#1 and contain { dac_override } Expected results: * the scenario does not trigger SELinux denials * write is allowed to the group owner of /var/lib/webalizer and /var/www/usage directories Additional info:
this is a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1382785 which already have more 3 dup reports (996305 1399501 1520587 ) before close as duplicated , can you do a patch for package ? , or an pull request ? , I personally disable SELINUX and don't have acknowledgment to do that
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Of course, link to PR: https://github.com/fedora-selinux/selinux-policy-contrib/pull/140
Thank you, do you know, when fedora-selinux with this patches will land on Fedora / EPEL ?
(In reply to Richard Fiľo from comment #3) > Of course, link to PR: > https://github.com/fedora-selinux/selinux-policy-contrib/pull/140 Hi, Richard in https://github.com/fedora-selinux/selinux-policy-contrib/pull/140 have we rules for [1] ? Thank you . [1] https://bugzilla.redhat.com/show_bug.cgi?id=1382785
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.