Skip to content

fix: correct warning instructions for admin-only ptrace audit.#2035

Open
jherzstein wants to merge 5 commits intosecureblue:livefrom
jherzstein:fix/admin-only-ptrace-audit
Open

fix: correct warning instructions for admin-only ptrace audit.#2035
jherzstein wants to merge 5 commits intosecureblue:livefrom
jherzstein:fix/admin-only-ptrace-audit

Conversation

@jherzstein
Copy link
Copy Markdown
Contributor

In the current ptrace audit, in the case where ptrace_scope=2, it will display the same warning as restricted ptrace.

The audit instructs the user to run toggle-ptrace-scope to forbid ptrace while ptrace_scope=2, but this will do the opposite and set ptrace_scope=1.

The warning must instruct the user must run it twice instead, and also indicate it is in admin-only ptrace instead of restricted ptrace.

Comment thread files/system/usr/libexec/secureblue/audit_secureblue.py Outdated
@jherzstein jherzstein force-pushed the fix/admin-only-ptrace-audit branch from dea9452 to 2361b5c Compare March 16, 2026 23:08
@jherzstein jherzstein requested a review from spaceoden March 16, 2026 23:11
Comment thread files/system/usr/libexec/secureblue/audit_secureblue.py Outdated
@jherzstein jherzstein requested a review from HastD March 21, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants