mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3753] [Feature] different profiles/behavior per user? #2366
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#2366
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 @hlein on GitHub (Nov 14, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3753
This is a request for advice that might turn into a feature request. I'm probably not the first to ask, but I couldn't find a previous discussion on this.
I would like firejail to behave differently for different users. Does the profile syntax have support for testing the current user or group memberships, and enabling/disabling things based on that? If not, what would be some options to accomplish that, and/or features that would need to be added to firejail?
For instance, on Gentoo, builds are done as user portage. In order for that to work, it needs various things that other system users (including myself!) do not need, such as,
wgetneeds to be able to write to/var/cache/distfiles/, pass ridiculously large environment variables (which currently requires changingfirejail.hand recompiling, but that's another matter ;), and a few other things I'm still discovering. Meanwhile, users that run certain services could have their profiles restricted still further. On some multiuser systems, I might want to restrict some regular users more than others, etc.I see
/etc/firejail/login.users, that's not what I'm after, but I suppose something similar that applied extra or alternate profile-files any time a named user ran a program via firejail might do it.I can see some workarounds with alternate paths for firejail symlinks (created by
firecfg --bindiror similar), that get added to different users' PATHs based on dotfiles, etc., and/or multiple compiled copies of firejail that look in different/etc/firejail/*/subdirs, but that'd be pretty messy and require custom upkeep.@rusty-snake commented on GitHub (Nov 14, 2020):
You can create profile overrides or add profiles to
$HOME/.config/firejail.@hlein commented on GitHub (Nov 14, 2020):
Duh, good call, that's a good start anyway; will be back if I run into things it isn't sufficient for.
@rusty-snake commented on GitHub (Jan 4, 2021):
I'm closing here due to inactivity, please fell free to request to reopen if you have more questions.