mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1388] 2 gotchas with whitelist (ending / and origin dir of a symlinked file) #949
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#949
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 @liloman on GitHub (Jul 16, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1388
Hi,
Another round of problems solving: :)
I reckon It should work as usual.
And then in your profile:
It properly whitelists:
test/
test/myfile
But it doesn't whitelist:
test-sym/
This scenario is my normal setting. :)
Cheers and greetings. :)
@Fred-Barclay commented on GitHub (Nov 8, 2017):
G'day @liloman !
1 works normally on my system. I haven't been able to test # 2 yet.
Since we've had the 0.9.50 release after your post, would it be possible for you to test this again and see if the problems remain?
Thanks!
Fred
@liloman commented on GitHub (Nov 9, 2017):
➬firejail --version
firejail version 0.9.51
Compile time support:
- AppArmor support is disabled
- AppImage support is enabled
- bind support is enabled
- chroot support is enabled
- file and directory whitelisting support is enabled
- file transfer support is disabled
- git install support is disabled
- networking support is enabled
- overlayfs support is enabled
- private-home support is enabled
- seccomp-bpf support is enabled
- user namespace support is enabled
- X11 sandboxing support is disabled
I confirm that I still have the two issues.
I can't whitelist a dir ending with "/" and It doesn't whitelist the realpath of the symlink. :)
Cheers and thanks!!!
@Fred-Barclay commented on GitHub (Nov 10, 2017):
What distro is this?
@liloman commented on GitHub (Nov 15, 2017):
Fedora 24.
@curiosity-seeker commented on GitHub (Nov 16, 2017):
You know that Fedora 24 is EOL?
See https://fedoramagazine.org/fedora-24-eol/
@chiraag-nataraj commented on GitHub (Aug 20, 2018):
@liloman Is this still an issue?
@chiraag-nataraj commented on GitHub (Aug 22, 2018):
Closing for inactivity. @liloman, please feel free to re-open if you still have this issue.
@bircoph commented on GitHub (Oct 31, 2018):
I have issue №2 with firejail-0.9.56 on Gentoo:
I have some directories in $HOME an symlinks, e.g.:
.config -> .private/.configAnd now whitelists and blacklists for files within .config doesn't work properly:
$ firejail --profile=/etc/firejail/firefox.profile bash:As can be seen files within .private/.config are set normally, but .config symlinks is not preserved. The only dir "dconf" is there because of the following in whitelist-common.inc:
If I comment mkdir line, then .config directory is not created at all.
For now as a workaround I added a script which creates all necessary symlinks before running firefox, but this affects other applications as well and the bug is very annoying. Please fix it by preserving all parent symlinks when necessary.
@SkewedZeppelin commented on GitHub (Oct 31, 2018):
@bircoph if you are using ecryptfs for that .private directory, consider switching to full home directory encryption (ecryptfs-migrate-home) instead as cleaner workaround for now.
slight ot: also see https://defuse.ca/audits/ecryptfs.htm
@bircoph commented on GitHub (Oct 31, 2018):
No, I do not use ecryptfs. I use LUKS, though I do not want to encrypt full home due to various reasons.
@chiraag-nataraj commented on GitHub (May 21, 2019):
LUKS shouldn't affect this. Is this still an issue?
@rusty-snake commented on GitHub (Aug 22, 2019):
@liloman @bircoph
I'm closing here due to inactivity, please fell free to reopen if you still have this issue.