mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #121] Can't whitelist subdirectories #80
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#80
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 @ghost on GitHub (Nov 6, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/121
I can't whitelist a subdirectory of a directory in my $HOME. That is, whitelisting ~/dir works, but ~/dir/subdir doesn't work. There is no error/warning on firejail invocation, but upon trying to enter the subdirectory, permission is denied.
If I try to also whitelist the parent directory, I get "Error mkdir:whitelist_path(99): File exists". Whitelisting the parent directory only, works.
I discovered this while wanting to whitelist ~/.config/deadbeef and deadbeef curiously failed to start, but started correctly when not whitelisted.
My version is 0.9.32
Example:
@netblue30 commented on GitHub (Nov 9, 2015):
I would suggest you move to version 0.9.34, it has quite a number of fixes. This is how I start deadbeef on my machine:
It also works with whitelisting:
@ghost commented on GitHub (Nov 10, 2015):
Sorry I take so long, I was very busy. I'll test it soon, but I believe you when you say it is fixed.
@netblue30 commented on GitHub (Nov 10, 2015):
No problem, give it a try and let me know.
@ghost commented on GitHub (Nov 11, 2015):
Just updated to 0.9.34
For some reason it still doesn't work.
I get this:
I tried some variations of the whitelist path, namely
and it all yielded the same result.
Again, when trying to cd into .config/, I get Permission denied. Whitelisting .config/ only, works.
Edit: Added debug.log
debug_log.txt
@netblue30 commented on GitHub (Nov 12, 2015):
You need a full path in --whitelist. Instead of "--whitelist=.config/deadbeef/", put "--whitelist=~/.config/deadbeef/"
@ghost commented on GitHub (Nov 12, 2015):
Yeah that's what I tried. They're all equivalent.
Anyway, I'll try fixing it myself. Not sure why it is a problem for me but seemingly no one else, but alright.