|Summary:||kadmind is not able to write to /var/kerberos/krbkdc/principal.ok file|
|Product:||Red Hat Enterprise Linux 5||Reporter:||Daniel Walsh <dwalsh>|
|Component:||selinux-policy||Assignee:||Daniel Walsh <dwalsh>|
|Status:||CLOSED ERRATA||QA Contact:|
|Version:||5.2||CC:||dkelson, mmalik, nalin, ohudlick|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-01-20 21:32:10 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Daniel Walsh 2008-07-11 15:46:59 UTC
Description of problem: This is a problem with the file labeling as well as kerberos not creating it with the correct label at creation. File should be labeled krbkdc_lock_t and kadmin and krb5kdc should be able to write/lock this file.
Comment 1 RHEL Product and Program Management 2008-07-11 15:59:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Comment 3 Daniel Walsh 2008-07-16 18:35:01 UTC
Fixed in selinux-policy-2.4.6-142.el5
Comment 7 Dax Kelson 2008-10-14 20:28:52 UTC
When is this going to be released as an errata package? This is biting us.
Comment 8 Dax Kelson 2008-10-14 20:44:42 UTC
Also which type is correct? krbkdc_lock_t or krb5kdc_principal_t
Comment 9 Daniel Walsh 2008-10-15 01:50:46 UTC
You can down load preview copies from http://people.redhat.com/dwalsh/SELinux/RHEL5/
Comment 12 errata-xmlrpc 2009-01-20 21:32:10 UTC
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0163.html