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.

+++ This bug was initially created as a clone of Bug #1421075 +++

Description of problem:
All rules which allow the ptrace operation should be controlled via the deny_ptrace boolean.
* https://fedoraproject.org/wiki/Features/SELinuxDenyPtrace

Version-Release number of selected component (if applicable):
selinux-policy-3.14.3-39.el8.noarch
selinux-policy-targeted-3.14.3-39.el8.noarch
selinux-policy-mls-3.14.3-39.el8.noarch
selinux-policy-devel-3.14.3-39.el8.noarch

How reproducible:
* always

Steps to Reproduce:
# sesearch --allow -p ptrace | grep -v deny_ptrace | grep allow
allow staff_t wireshark_t:process { getattr ptrace sigchld sigkill signal signull sigstop transition };
allow svirt_t svirt_t:process { fork getcap getsched ptrace setrlimit setsched sigchld sigkill signal signull sigstop };
allow sysadm_t lockdev_t:process { getattr ptrace sigchld sigkill signal signull sigstop transition };
allow sysadm_t wireshark_t:process { getattr ptrace sigchld sigkill signal signull sigstop transition };
#

Actual results:
* the output of above-mentioned command contains 4 allow rules

Expected results:
* the output of above-mentioned command is empty

The expectation that all ptrace permissions should be controlled by the deny_ptrace boolean is correct, changing the behaviour in the middle of RHEL 8 lifecycle though means a nonnegligible regression risk, especially for virt domains:

allow svirt_t svirt_t:process { fork getcap getsched ptrace setrlimit setsched sigchld sigkill signal signull sigstop };

hence retargetting to RHEL 9.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.