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:
SELinux policy prevents postfix to contact 389ds ever a unix domain socket.
Version-Release number of selected component (if applicable):
postfix-3.3.1-12
How reproducible:
Always
Steps to Reproduce:
1. Tell postfix to bind to an LDAP server over a unix domain socket as follows:
server_host = ldapi://%2fvar%2frun%2fslapd-gatekeeper.socket
2. Start postfix
3.
Actual results:
Postfix fails to connect to LDAP server, with permission denied from selinux:
type=AVC msg=audit(1601463793.905:17140): avc: denied { write } for pid=14790 comm="cleanup" name="slapd-gatekeeper.socket" dev="tmpfs" ino=31217 scontext=system_u:system_r:postfix_cleanup_t:s0 tcontext=system_u:object_r:dirsrv_var_run_t:s0 tclass=sock_file permissive=0
Expected results:
SELinux works properly, postfix succeeds in contacting LDAP server.
Additional info:
Comment 2RHEL Program Management
2022-03-30 07:27:28 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Looks like your bot auto-closed a lot of tickets.
This is trivial to fix, please sort it out.
Comment 6RHEL Program Management
2022-09-30 07:27:54 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: SELinux policy prevents postfix to contact 389ds ever a unix domain socket. Version-Release number of selected component (if applicable): postfix-3.3.1-12 How reproducible: Always Steps to Reproduce: 1. Tell postfix to bind to an LDAP server over a unix domain socket as follows: server_host = ldapi://%2fvar%2frun%2fslapd-gatekeeper.socket 2. Start postfix 3. Actual results: Postfix fails to connect to LDAP server, with permission denied from selinux: type=AVC msg=audit(1601463793.905:17140): avc: denied { write } for pid=14790 comm="cleanup" name="slapd-gatekeeper.socket" dev="tmpfs" ino=31217 scontext=system_u:system_r:postfix_cleanup_t:s0 tcontext=system_u:object_r:dirsrv_var_run_t:s0 tclass=sock_file permissive=0 Expected results: SELinux works properly, postfix succeeds in contacting LDAP server. Additional info: