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:
Someone renamed matahari-net init script to matahari-network, but did not tell SELinux guys about it. Which means that matahari-network init script is now labelled initrc_exec_t instead of matahari_initrc_exec_t.
Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-115.el6.noarch
selinux-policy-minimum-3.7.19-115.el6.noarch
selinux-policy-doc-3.7.19-115.el6.noarch
selinux-policy-targeted-3.7.19-115.el6.noarch
selinux-policy-mls-3.7.19-115.el6.noarch
matahari-lib-0.4.4-2.el6.x86_64
matahari-network-0.4.4-2.el6.x86_64
matahari-debuginfo-0.4.4-2.el6.x86_64
matahari-broker-0.4.4-2.el6.x86_64
matahari-sysconfig-0.4.4-2.el6.x86_64
matahari-agent-lib-0.4.4-2.el6.x86_64
matahari-host-0.4.4-2.el6.x86_64
matahari-0.4.4-2.el6.x86_64
matahari-consoles-0.4.4-2.el6.x86_64
matahari-service-0.4.4-2.el6.x86_64
Steps to Reproduce:
# matchpathcon /etc/rc.d/init.d/matahari-net
/etc/rc.d/init.d/matahari-net system_u:object_r:matahari_initrc_exec_t:s0
# matchpathcon /etc/rc.d/init.d/matahari-network
/etc/rc.d/init.d/matahari-network system_u:object_r:initrc_exec_t:s0
#
Actual results:
# matchpathcon /etc/rc.d/init.d/matahari-*
/etc/rc.d/init.d/matahari-broker system_u:object_r:initrc_exec_t:s0
/etc/rc.d/init.d/matahari-host system_u:object_r:matahari_initrc_exec_t:s0
/etc/rc.d/init.d/matahari-network system_u:object_r:initrc_exec_t:s0
/etc/rc.d/init.d/matahari-service system_u:object_r:matahari_initrc_exec_t:s0
/etc/rc.d/init.d/matahari-sysconfig system_u:object_r:initrc_exec_t:s0
/etc/rc.d/init.d/matahari-sysconfig-console system_u:object_r:initrc_exec_t:s0
Expected results:
* all matahari init scripts are labelled matahari_initrc_exec_t
Unfortunately following binaries were also renamed which means they are all labelled bin_t now.
# matchpathcon /usr/sbin/matahari-*
/usr/sbin/matahari-brokerd system_u:object_r:bin_t:s0
/usr/sbin/matahari-dbus-hostd system_u:object_r:bin_t:s0
/usr/sbin/matahari-dbus-networkd system_u:object_r:bin_t:s0
/usr/sbin/matahari-dbus-serviced system_u:object_r:bin_t:s0
/usr/sbin/matahari-qmf-hostd system_u:object_r:bin_t:s0
/usr/sbin/matahari-qmf-networkd system_u:object_r:bin_t:s0
/usr/sbin/matahari-qmf-service-cli system_u:object_r:bin_t:s0
/usr/sbin/matahari-qmf-serviced system_u:object_r:bin_t:s0
/usr/sbin/matahari-qmf-sysconfig-consoled system_u:object_r:bin_t:s0
/usr/sbin/matahari-qmf-sysconfigd system_u:object_r:bin_t:s0
#
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