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.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0526.html
Description of problem: user_u confined users should be allowed to ping if the user_ping boolean is enabled. The boolean is in the SELinux policy, but user_u confined users cannot ping even if it is enabled. Version-Release number of selected component (if applicable): selinux-policy-3.7.19-54.el6_0.3.noarch How reproducible: 100% Steps to Reproduce: 1. # yum -y install policycoreutils-python 2. # useradd -Z user_u joe_user && echo redhat | passwd --stdin joe_user 3. # setsebool -P user_ping 1 4. Log in as joe_user. 5. % ping localhost Actual results: AVC denial. # getsebool user_ping user_ping --> on # tail -4 /var/log/audit/audit.log | audit2allow #============= user_t ============== allow user_t self:capability setuid; allow user_t self:rawip_socket create; ~~~ type=AVC msg=audit(1292273650.392:24629): avc: denied { create } for pid=28941 comm="ping" scontext=user_u:user_r:user_t:s0 tcontext=user_u:user_r:user_t:s0 tclass=rawip_socket type=SYSCALL msg=audit(1292273650.392:24629): arch=c000003e syscall=41 success=no exit=-13 a0=2 a1=3 a2=1 a3=c items=0 ppid=28917 pid=28941 auid=504 uid=504 gid=504 euid=0 suid=0 fsuid=0 egid=504 sgid=504 fsgid=504 tty=pts1 ses=45 comm="ping" exe="/bin/ping" subj=user_u:user_r:user_t:s0 key=(null) type=AVC msg=audit(1292273650.393:24630): avc: denied { setuid } for pid=28941 comm="ping" capability=7 scontext=user_u:user_r:user_t:s0 tcontext=user_u:user_r:user_t:s0 tclass=capability type=SYSCALL msg=audit(1292273650.393:24630): arch=c000003e syscall=105 success=yes exit=0 a0=1f8 a1=d a2=609ce8 a3=c items=0 ppid=28917 pid=28941 auid=504 uid=504 gid=504 euid=504 suid=0 fsuid=504 egid=504 sgid=504 fsgid=504 tty=pts1 ses=45 comm="ping" exe="/bin/ping" subj=user_u:user_r:user_t:s0 key=(null) ~~~ Expected results: user_u confine user can ping if boolean is enabled.