mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #128] Whitelisting symbolic links whitelists the source file but not the symlink #85
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#85
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 @0nse on GitHub (Nov 10, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/128
I'm currently running Firejail 0.9.34 from the AUR. Whenever there is a
whitelistentry in a profile, the program will basically not be able to access anything.For example, Firefox will load with the default GTK theme and not have access to my vimperator configuration, when there is any whitelist entry. This sounds reasonable at first, but adding the relevant files—which is now done in the upstream configuration— does not change this behaviour (
~/.vimperator,~/.vimperatorrc,~/.gtkrc-2.0,~/..config/gtk-3.0/settings.ini). When navigating in Firefox browsing my local disk usingfile:///, I see the file names but cannot access them.This happens for all programs I have tested so far: Firefox, Chromium and Pidgin. The browsers are still able to load their profiles, probably because these folders are added as
noblacklist.@netblue30 commented on GitHub (Nov 10, 2015):
I keep on the main page of the project here on github the current whitelist for Firefox. Only these files/directories are visible in your /home/user directory.
.config/gtk-03 directory was added yesterday in the development version.
Files and dirs in the rest of the system are still visible, most of them are read-only, other are empty files and cannot be opened (blacklist).
@0nse commented on GitHub (Nov 10, 2015):
Regarding GTK3: Yes, that's correct and I am aware of that. I had manipulated the profile files myself to whitelist it. However, entries that I have put on whitelist (or that already have been, like~/.vimperatorrc) are not accessible in Firefox. They are missing infile:///and only if I remove all whitelist entries, they become readable again.I get and like the idea of mounting a new home with fewer contents. But whitelisting anything will not lead to those entries appearing in my program-specific new home directory.Edit: Actually some whitelist entries seem to work. It looks quite random. With the default configuration from0.9.34I have in my new home.zoterobut e.g. not.vimperatorrc.Further inspections make me believe that symbolic links are a problem with whitelists. I have
.gtkrc-2.0and other files as a symlink under~. What Firejail now does is, it whitelists the source file but removes the symbolic link. Thus, Firefox won't find~/.gtkrc-2.0but instead will show~/Documents/dotfiles/gtk/.gtkrc-2.0.@netblue30 commented on GitHub (Nov 10, 2015):
OK, that's a bug, I'll have to fix it, thanks.
@netblue30 commented on GitHub (Nov 11, 2015):
Fixed.
@0nse commented on GitHub (Feb 7, 2016):
I experience this behaviour again in 0.9.38.
@netblue30 commented on GitHub (Feb 8, 2016):
What are you trying to do?
@0nse commented on GitHub (Feb 8, 2016):
I found that I have to whitelist a parent directory in my home directory in which the files are located whose symlinks are whitelisted by the default config. Imagine the following symlink:
If I don't whitelist
~/dotfiles,~/.gtkrc-2.0cannot be read.On a sidenote: when that happens, Firefox often removes all contents from that file while starting. Anyways, I could solve my own problem and thus close this ticket. Thanks!