Hide Forgot
Description of problem: corosync-notifyd does not have it's own policy and keeps initrc_t after startup Version-Release number of selected component (if applicable): selinux-policy-3.7.19-82.el6.noarch How reproducible: 100% Steps to Reproduce: 1.service corosync-notifyd start 2. 3. Actual results: initrc_t context Expected results: corosync-notifyd's own context Additional info: This is needed together with foghorn policy (bug 693792) to have full selinux coverage of added cluster SNMP functionality.
If this is not causing any AVC's I believe we should put this off until 6.2
Jaroslav, I am not seeing AVC msgs, can you confirm it with your configuration? You could also try to play with the following labeling chcon -t corosync_exec_t /usr/sbin/corosync-notifyd which I believe it could also work.
I've not noticed any denial (yet), but that's IMHO not surprising in initrc_t context.
Well, actually there could be AVC msgs. Other cluster domains could talk with this daemon which could cause issues.
Fixed in selinux-policy-3.7.19-101.el6
Fixed in selinux-policy-3.7.19-106.el6
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