Description of problem: Version-Release number of selected component (if applicable): selinux-policy-targeted-3.7.19-155.el6_3.noarch selinux-policy-doc-3.7.19-155.el6_3.noarch selinux-policy-minimum-3.7.19-155.el6_3.noarch selinux-policy-mls-3.7.19-155.el6_3.noarch selinux-policy-3.7.19-155.el6_3.noarch How reproducible: always Steps to Reproduce: # yum -y install rhnsd # run_init service rhnsd restart # ps -efZ | grep rhnsd Actual results: system_u:system_r:initrc_t:s0 root 28048 1 0 03:36 ? 00:00:00 rhnsd Expected results: * rhnsd runs in its own SELinux domain
Created attachment 594162 [details] basic policy for rhnsd
No AVCs appeared even if I used start, stop, restart actions.
Could we treat it with rhsmcertd policy? # chcon -t rhsmcertd_exec_t `which rhnsd`
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
(In reply to comment #4) > Could we treat it with rhsmcertd policy? > > # chcon -t rhsmcertd_exec_t `which rhnsd` It seems so. I see no AVCs after "service rhnsd restart".
... and the daemon runs as rhsmcertd_t in enforcing mode.
Great.
(In reply to comment #8) > ... and the daemon runs as rhsmcertd_t in enforcing mode. Users tend to not care about running. They care about serving.
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-2013-0314.html