mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #873] Use of systemcalls #589
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#589
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 @valoq on GitHub (Oct 26, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/873
Analysing the systemcalls of mupdf and writing code which applies those syscalls with seccomp filter (using libseccomp) and the executing mupdf, I got a working application with only very few allowed syscalls.
However simply applying thoses syscalls to firejail with seccomp.keep does not work and it turns out that with firejail, mupdf needs a lot more syscalls. Why is that?
@netblue30 commented on GitHub (Oct 27, 2016):
After the filter is enabled, the sandbox still makes a small number of syscalls in order to configure and monitor the program running in the sandbox.