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.
Umm, for some reason even the second attempt did not reproduce it. I'm out of ideas.
Note that at this point a workaround has been applied, so JFTR: third and further attempts would have to be accompanied by:
distribution_hack__policy=skip
so that the hack (which adds ad-hoc module) would not be applied.
We have fixes in Fedora:
commit 36196ffa702f7e64b26c4fbde4fe4b71e00348d9 (HEAD -> rawhide, origin/rawhide, origin/HEAD)
Author: Nikola Knazekova <nknazeko>
Date: Thu Jul 25 10:12:10 2019 +0200
Allow httpd_t to signull mailman_cgi_t process
Allow httpd_t to test for existence of mailman_cgi_t process without sending a signal.
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.
https://access.redhat.com/errata/RHBA-2020:1773
Description of problem ====================== When enabling Web UI for mailman, we get this AVC: type=PROCTITLE msg=audit(1551892512.795:1229): proctitle=2F7573722F7362696E2F6874747064002D44464F524547524F554E44 type=SYSCALL msg=audit(1551892512.795:1229): arch=c000003e syscall=62 success=no exit=-13 a0=5bcc a1=0 a2=7ff008008a60 a3=7ff017e64520 items=0 ppid=23273 pid=23275 auid=4294967295 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="httpd" exe="/usr/sbin/httpd" subj=system_u:system_r:httpd_t:s0 key=(null) type=AVC msg=audit(1551892512.795:1229): avc: denied { signull } for pid=23275 comm="httpd" scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:system_r:mailman_cgi_t:s0 tclass=process permissive=0 audit2allow: allow httpd_t mailman_cgi_t:process signull; Version-Release number of selected component ============================================ selinux-policy-3.14.1-61.el8 How reproducible ================ Almost always Steps to Reproduce ================== Schedule /CoreOS/mailman/Sanity/dmarc-support-ui Actual results ============== Mentioned AVC Expected results ================ No AVC. Additional info =============== Scheduled separately with permissive/enforcing https://beaker.engineering.redhat.com/matrix/?toggle_nacks_on=on&job_ids=3400604+3400601