Bug 1995425

Summary: sa-update.service encountering SELinux denials
Product: [Fedora] Fedora Reporter: Bojan Smojver <bojan>
Component: spamassassinAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 34CC: abo, daniel, jskarvad, kevin, mail, nb, olysonek-foss, pavel
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 22:54:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bojan Smojver 2021-08-19 05:41:30 UTC
Description of problem:

Additional SELinux permissions required to run sa-update.service.

Version-Release number of selected component (if applicable):
spamassassin-3.4.6-1.fc34.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. systemctl start sa-update.service (or wait for timer to kick it off).

Actual results:
SELinux denials.

Expected results:
There should be none.

Additional info:

This is required on SELinux side for denials to be avoided:
-----
require {
                type admin_home_t;
                type systemd_unit_file_t;
                type spamd_update_t;
                type init_t;
                class dir { add_name create write };
                class service { start status };
                class file getattr;
                class system status;
}
 
#============= spamd_update_t ==============
allow spamd_update_t admin_home_t:dir { add_name create write };
allow spamd_update_t init_t:system status;
allow spamd_update_t systemd_unit_file_t:file getattr;
allow spamd_update_t systemd_unit_file_t:service { start status };
-----

Comment 1 Silvan Nagl 2022-03-22 09:12:05 UTC
Still present on Fedora 35.

Comment 2 Ben Cotton 2022-05-12 15:59:24 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-07 22:54:23 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

Thank you for reporting this bug and we are sorry it could not be fixed.