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.
DescriptionJonathan Underwood
2011-06-14 17:27:53 UTC
Description of problem:
Currently SElinux policy forbids kadmind from communicating with slapd via ldapi.
Version-Release number of selected component (if applicable):
libselinux-2.0.94-2.el6.x86_64
libselinux-utils-2.0.94-2.el6.x86_64
selinux-policy-3.7.19-54.el6_0.5.noarch
libselinux-ruby-2.0.94-2.el6.x86_64
selinux-policy-targeted-3.7.19-54.el6_0.5.noarch
krb5-server-1.8.2-3.el6_0.7.x86_64
krb5-server-ldap-1.8.2-3.el6_0.7.x86_64
krb5-workstation-1.8.2-3.el6_0.7.x86_64
krb5-libs-1.8.2-3.el6_0.7.x86_64
openldap-2.4.19-15.el6_0.2.x86_64
openldap-servers-2.4.19-15.el6_0.2.x86_64
openldap-clients-2.4.19-15.el6_0.2.x86_64
How reproducible:
Everytime
Steps to Reproduce:
1.Configure krb5.conf such that kadmin it is communicating to a backend openldap database on same host
2. Try to start kadmin service
3.
Actual results:
Starting Kerberos 5 Admin Server: kadmind: Can't contact LDAP server while initializing, aborting
Expected results:
kadmin service starts
Additional info:
setenforce 0 does allow kadmin to start. Basically we need to allow kadmind to communicate with slapd via a socket (/var/run/ldapi)
Generating an selinux module with:
grep kadmin audit.log | audit2allow -M kadminldapilocal
produces the following kadminldapilocal.te
module kadminldapilocal 1.0;
require {
type slapd_t;
type slapd_var_run_t;
type kadmind_t;
class sock_file write;
class unix_stream_socket connectto;
}
#============= kadmind_t ==============
allow kadmind_t slapd_t:unix_stream_socket connectto;
allow kadmind_t slapd_var_run_t:sock_file write;
Comment 1Jonathan Underwood
2011-06-14 17:30:22 UTC
I think this is fixed in the 6.1 policy. I know it is in
selinux-policy-3.7.19-98.el6 which is the preview of the 6.2 policy.
Preview available on people.redhat.com/dwalsh/SELinux/RHEL6
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-2011-1511.html
Description of problem: Currently SElinux policy forbids kadmind from communicating with slapd via ldapi. Version-Release number of selected component (if applicable): libselinux-2.0.94-2.el6.x86_64 libselinux-utils-2.0.94-2.el6.x86_64 selinux-policy-3.7.19-54.el6_0.5.noarch libselinux-ruby-2.0.94-2.el6.x86_64 selinux-policy-targeted-3.7.19-54.el6_0.5.noarch krb5-server-1.8.2-3.el6_0.7.x86_64 krb5-server-ldap-1.8.2-3.el6_0.7.x86_64 krb5-workstation-1.8.2-3.el6_0.7.x86_64 krb5-libs-1.8.2-3.el6_0.7.x86_64 openldap-2.4.19-15.el6_0.2.x86_64 openldap-servers-2.4.19-15.el6_0.2.x86_64 openldap-clients-2.4.19-15.el6_0.2.x86_64 How reproducible: Everytime Steps to Reproduce: 1.Configure krb5.conf such that kadmin it is communicating to a backend openldap database on same host 2. Try to start kadmin service 3. Actual results: Starting Kerberos 5 Admin Server: kadmind: Can't contact LDAP server while initializing, aborting Expected results: kadmin service starts Additional info: setenforce 0 does allow kadmin to start. Basically we need to allow kadmind to communicate with slapd via a socket (/var/run/ldapi) Generating an selinux module with: grep kadmin audit.log | audit2allow -M kadminldapilocal produces the following kadminldapilocal.te module kadminldapilocal 1.0; require { type slapd_t; type slapd_var_run_t; type kadmind_t; class sock_file write; class unix_stream_socket connectto; } #============= kadmind_t ============== allow kadmind_t slapd_t:unix_stream_socket connectto; allow kadmind_t slapd_var_run_t:sock_file write;