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:
Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.7.19-145.el6.noarch
selinux-policy-doc-3.7.19-145.el6.noarch
selinux-policy-mls-3.7.19-145.el6.noarch
selinux-policy-3.7.19-145.el6.noarch
selinux-policy-minimum-3.7.19-145.el6.noarch
rusers-server-0.17-61.el6.x86_64
How reproducible:
always
Steps to Reproduce:
# service rusersd status
rpc.rusersd is stopped
# service rstatd status
rpc.rstatd is stopped
# run_init service rusersd start
Authenticating root.
Password:
Starting rusers services: [ OK ]
# run_init service rstatd start
Authenticating root.
Password:
Starting rstat services: [ OK ]
# service rusersd status
rpc.rusersd (pid 14248) is running...
# service rstatd status
rpc.rstatd (pid 14266) is running...
# ps -efZ | grep initrc_t
system_u:system_r:initrc_t:s0 nobody 14248 1 0 20:42 ? 00:00:00 rpc.rusersd
system_u:system_r:initrc_t:s0 root 14266 1 0 20:42 ? 00:00:00 rpc.rstatd
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 14292 12100 0 20:42 pts/1 00:00:00 grep initrc_t
#
Actual results:
* both rpc.rstatd and rpc.rusersd run as initrc_t
Expected results:
* both rpc.rstatd and rpc.rusersd run in their own SELinux domain
The daemon is not confined by SELinux. Please help SELinux folks to create a suitable policy module. You know that we should minimize the number of programs running as initrc_t, don't you?
I tried to sum up some potential SELinux-related actions. However, re-assigning to selinux-policy, since I'm not able to write the rules myself. Hope the following helps; if any questions, just ask.
rstatd:
* daemonizes: fork + setsid
* writes log messages to Syslog
* reads /proc/stat
* reads /proc/net/dev
* reads /proc/diskstats
* reads /proc/uptime
* reads /proc/loadavg
* registers rpcbind services (udp socket):
100001 3 udp rstatd
100001 2 udp rstatd
100001 1 udp rstatd
rusersd:
* daemonizes: fork + setsid
* writes log messages to Syslog
* getutent()
* stat(/dev/ttyX)
* registers rpcbind services (udp socket):
100002 3 udp rusersd
100002 2 udp rusersd
Comment 3RHEL Program Management
2012-07-10 08:19:54 UTC
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.
Comment 4RHEL Program Management
2012-07-11 01:55:45 UTC
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.