mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #837] relax ptrace + seccomp restrictions on 4.8 kernel? #570
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#570
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.