mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1095] Firefox extension accessing non-whitelisted folder #750
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#750
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 @mustaqimM on GitHub (Feb 9, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1095
I manually added my KeePass folder in KeeFox, ie. ~/.KeePass, and it's able to access it even though Firefox is using the default firejail profile. Is this normal for extensions to be granted unrestricted access?
@chiraag-nataraj commented on GitHub (Feb 9, 2017):
The default profile whitelists ~/.keepassx (at least in the version I have). Or did you actually mean ~/.KeePass? I will try installing the addon to see what happens.
@mustaqimM commented on GitHub (Feb 10, 2017):
@chiraag-nataraj I downloaded the portable version and moved the contents to my own folder:
~/.KeePass. I didn't whitelist it@netblue30 commented on GitHub (Feb 11, 2017):
This could be a possible problem: https://firejail.wordpress.com/support/frequently-asked-questions/#firefox
The first firefox instance takes over any subsequent instances. You need to make sure you are not already running firefox when you start the sandbox.
@mustaqimM commented on GitHub (Feb 12, 2017):
@netblue30 I only launch a single instance with firejail, firejail is indeed running since I am able to only access the
~/Downloadsfolder among others http://i.imgur.com/5CHbRmD.png. I can't choose the~/.KeePassfolder from the open dialog in the KeeFox extension but if I manually add it: http://i.imgur.com/6bB1eeg.png, then I am able to use it with KeeFox@netblue30 commented on GitHub (Feb 12, 2017):
What distro are you using? Also, give me some links to Firefox addon and keepass portable you have installed, I'll give it a try.
@mustaqimM commented on GitHub (Feb 13, 2017):
@netblue30 I'm currently on Antergos (arch linux). The addon is here (1.4.1) and the portable KeePass is here (2.35)
@SYN-cook commented on GitHub (Mar 1, 2017):
@mustaqimM The reason is that Keepass and KeeFox communicate with each other as local server and local client. Or in other words: KeeFox uses Keepass to access the password store, it doesn't access the password store directly. There is no sandbox escape here.