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:
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