Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When running Postfix + Amavis + Spamassassin on RHEL6, restorecon reports these mislabeled files:
# restorecon -R -v -n /usr/bin
restorecon reset /usr/bin/razor-admin context system_u:object_r:spamc_exec_t:s0->system_u:object_r:razor_exec_t:s0
restorecon reset /usr/bin/razor-revoke context system_u:object_r:spamc_exec_t:s0->system_u:object_r:razor_exec_t:s0
restorecon reset /usr/bin/razor-client context system_u:object_r:spamc_exec_t:s0->system_u:object_r:razor_exec_t:s0
restorecon reset /usr/bin/razor-report context system_u:object_r:spamc_exec_t:s0->system_u:object_r:razor_exec_t:s0
restorecon reset /usr/bin/razor-check context system_u:object_r:spamc_exec_t:s0->system_u:object_r:razor_exec_t:s0
However, if I tell restorecon to relabel these files (i.e. remove the -n flag from the previous command), the files are immediately relabeled from razor_exec_t to spamc_exec_t.
It appears that either Amavis or Spamassassin is enforcing the labeling.
Version-Release number of selected component (if applicable):
# rpm -q selinux-policy
selinux-policy-3.7.19-126.el6_2.3.noarch
How reproducible:
Every time.
Steps to Reproduce:
1. Install/Configure amavisd-new (From EPEL) and install/configure Spamassassin
2. Start amavisd and spamd
3. Check labeling on the files in /usr/bin, try to fix the labels.
Additional Information:
I'm not sure if the correct fix is to change the selinux policy or to fix the applications.
It should also be noted that this mislabeling doesn't appear to be breaking anything. Our monitoring system is just watching for mislabeled files and alerted us to this issue.
This is happening because spamc_exec_t and razor_exec_t are alias files.
In order to fix this we really need to eliminate the razor.pp file altogether and just ship the file context in spamassassin.pp like we have in F17.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0780.html