Hide Forgot
Description of problem: * openwsmand uses too powerful SELinux domain Version-Release number of selected component (if applicable): openwsman-server-2.2.3-8.el6.x86_64 selinux-policy-3.7.19-231.el6.noarch selinux-policy-doc-3.7.19-231.el6.noarch selinux-policy-minimum-3.7.19-231.el6.noarch selinux-policy-mls-3.7.19-231.el6.noarch selinux-policy-targeted-3.7.19-231.el6.noarch How reproducible: always Steps to Reproduce: # touch /etc/openwsman/simple_auth.passwd # service openwsmand status Checking for service Openwsman Daemon stopped stopped # service openwsmand start Starting the Openwsman Daemon done. # service openwsmand status Checking for service Openwsman Daemon running # ps -efZ | grep openwsman unconfined_u:system_r:initrc_t:s0 root 26685 1 0 15:05 ? 00:00:00 /usr/sbin/openwsmand -S unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 26702 3863 0 15:05 pts/0 00:00:00 grep openwsman # Actual results: * openwsmand runs as initrc_t Expected results: * openwsmand runs in its own SELinux domain
We have it in RHEL7 openwsman.fc:/usr/sbin/openwsmand -- gen_context(system_u:object_r:openwsman_exec_t,s0)
sent patch
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-2014-1568.html