[GH-ISSUE #873] Use of systemcalls #589

Closed
opened 2026-05-05 06:14:13 -06:00 by gitea-mirror · 1 comment
Owner

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?

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?
gitea-mirror 2026-05-05 06:14:13 -06:00
Author
Owner

@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.

<!-- gh-comment-id:256659123 --> @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.
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#589
No description provided.