mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1088] Sandboxed daemon cannot mmap to kernel #743
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#743
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 @xplodwild on GitHub (Feb 3, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1088
Hi,
I'm currently trying to sandbox a daemon which mmap a shared library (.so) to kernel memory to save memory in case multiple instances are running. However, when running through firejail, the mmap2 call fails.
strace log when running
firejail --noprofile strace ./binas a normal user:However, when running
sudo firejail --noprofile strace ./bin, the binary runs fine and the library is mmap'd properly. Similarly, running./binwithout firejail works fine too.Am I missing something or is it a firejail bug?
Thanks!
@netblue30 commented on GitHub (Feb 8, 2017):
Does it work as "sudo firejail --noprofile ./bin" ?
@xplodwild commented on GitHub (Feb 13, 2017):
Yes, as mentionned in my issue, it works with
sudo firejail --noprofile ./bin,sudo ./bin,./bin, but notfirejail --noprofile ./bin@chiraag-nataraj commented on GitHub (Sep 30, 2018):
@xplodwild Is this still an issue?
@chiraag-nataraj commented on GitHub (May 21, 2019):
Going to close for inactivity. @xplodwild, please feel free to re-open if this is still an issue.