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:
Because mailman uses /etc/mailman/mm_cfg.py -> /usr/lib/mailman/Mailman/mm_cfg.py any change of that file makes python to rebuild .pyc file which is denied by selinux and produces AVC, see bz1054688.

Clean solution would be to swap file and link location.

Version-Release number of selected component (if applicable):
mailman-2.1.12-18.el6

How reproducible:
100%

Steps to Reproduce:
1. execute /CoreOS/mailman/Sanity/simple beaker task


Actual results:
time->Thu Jan 16 08:10:18 2014
type=SYSCALL msg=audit(1389877818.008:38): arch=80000015 syscall=10 success=no exit=-13 a0=fffea816ef7 a1=fffa8af1720 a2=7 a3=6f646500 items=0 ppid=23499 pid=23502 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mailmanctl" exe="/usr/bin/python" subj=unconfined_u:system_r:mailman_mail_t:s0 key=(null)
type=AVC msg=audit(1389877818.008:38): avc:  denied  { write } for  pid=23502 comm="mailmanctl" name="Mailman" dev=dm-0 ino=2896360 scontext=unconfined_u:system_r:mailman_mail_t:s0 tcontext=system_u:object_r:lib_t:s0 tclass=dir

Ideal situation from SELinux point of view:

/usr/lib/mailman/Mailman/mm_cfg.py -> /etc/mailman/mm_cfg.py

Because mailman SELinux domain is allowed to create / modify / delete files in /etc/mailman directory.

Changing the symlink order won't fix this bug, because mailman will still load mm_cfg.py from /usr/lib (even if it's symlink) and python will try to byte-compile it (even if it's symlink). The only way I know about how to fix that is byte-compile mm_cfg.py from mailman initscript before starting it.

*** This bug has been marked as a duplicate of bug 923340 ***