mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #110] Whitelist scripts to be executed #67
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#67
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 @blueyed on GitHub (Oct 29, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/110
I am using a script for the
editorsetting in Vimperator (a Firefox plugin):After whitelisting the script itself, it can be executed, but then fails because the shell's resource files (
~/.zshrcetc) are not readable.Adding
~/.zshrcto the whitelist does not work, probably because it's a symlink (see https://github.com/netblue30/firejail/issues/105#issuecomment-151809628), but it would probably require to also whitelist all files that get sourced from there.I wonder if it would be possible to have something like with ssh's
command=inauthorized_keysor insudoers, where you could whitelist some program to be executed. This way I could saywhitelist_program /path/to/vim-in-term.@netblue30 commented on GitHub (Oct 30, 2015):
If you go this way, you'll end up whitelisting everything in your home directory. Maybe a better way is to create a new directory and push it to firejail using --private=directory:
I use --private=directory myself.
@blueyed commented on GitHub (Nov 1, 2015):
Thanks for your support on this!
What about whitelisting programs, which would then run in the user's context, similar to what SSH allows with
command=?Maintaining a separate browser directory seems to be a bit overkill, when I want to only use an external editor (in a terminal).
@netblue30 commented on GitHub (Nov 2, 2015):
Something else you could do is --private-bin. This allows you to specify the content of your /bin directory. Example:
Replace iceweasel with firefox if necessary. Once the browser is open, type "/bin" in the url field, and it will show you the content of /bin directory. /sbin, /usr/bin and /usr/sbin look the same as /bin.
@blueyed commented on GitHub (Nov 2, 2015):
But will that include e.g. ~/.zshrc etc?
My idea is to allow for a whitelisted program to run in the "normal"/full context again.
@netblue30 commented on GitHub (Nov 3, 2015):
An example:
I bring in the sandbox my ~/work directory (requested by whitelist), .Xauthority (to get X11 running), and a default version of .bashrc (from /etc/skel directory). I guess I can bring in also a .zshrc, but I need a default one.