mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3980] private-lib: can we mount instead of copy? #2490
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#2490
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 @smitsohu on GitHub (Feb 12, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3980
While in general
privateoptions copy files in the sandbox instead of mounting them, there are two exceptions to the rule:private-tmp, which mounts a set of paths in the sandbox in order to provide essential socketsprivate-lib, which currently employs a mix of copying and mounting: files are copied and directories are mountedI would propose to move all of
private-libto mounts, mainly for performance reasons. For example it takes Firejail seconds to configure the sandboxfirejail --noprofile --private-lib kcalc, even on a rather powerful notebook. On legacy hardware it can be ten seconds and more. Switching from copying to mounting accelerates sandbox setup by about an order of magnitude.Resolving the inconsistency in the other direction, that is copy everything and mount nothing, is probably not going to work because of excessive RAM demand. Also it would slow down
private-libeven more.@reinerh commented on GitHub (Feb 12, 2021):
Mounting read-only?
@smitsohu commented on GitHub (Feb 12, 2021):
@reinerh If we remove the read-only flag, it would tear holes in Firejail's basic read-only file system. So read-only would be best, I guess.
@reinerh commented on GitHub (Feb 12, 2021):
Okay, thanks. Just wanted to clarify if it gets mounted read-only.
@netblue30 commented on GitHub (Feb 13, 2021):
Yes, I think we should clean it up and make it mount-only..