[GH-ISSUE #837] relax ptrace + seccomp restrictions on 4.8 kernel? #570

Closed
opened 2026-05-05 06:10:59 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @the8472 on GitHub (Oct 5, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/837

https://outflux.net/blog/archives/2016/10/04/security-things-in-linux-v4-8/

Aiui from 4.8 onwards ptrace from within jail should be ok. At least if tracing pid 1 in the jail (the firejail-child) is still blocked.

Originally created by @the8472 on GitHub (Oct 5, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/837 https://outflux.net/blog/archives/2016/10/04/security-things-in-linux-v4-8/ Aiui from 4.8 onwards ptrace from within jail should be ok. At least if tracing pid 1 in the jail (the firejail-child) is still blocked.
gitea-mirror 2026-05-05 06:10:59 -06:00
Author
Owner

@netblue30 commented on GitHub (Oct 6, 2016):

You can build a seccomp filter allowing ptrace today. We disable it in the default configuration because it would allow tracing the processes running inside the jail.

<!-- gh-comment-id:251942643 --> @netblue30 commented on GitHub (Oct 6, 2016): You can build a seccomp filter allowing ptrace today. We disable it in the default configuration because it would allow tracing the processes running inside the jail.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#570
No description provided.