mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #352] Firefox High Security Mode + Pipelight #248
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#248
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 @Gerii on GitHub (Mar 5, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/352
Is it possible to stop NPAPI plugins from starting with Firefox? I currently have Pipelight installed to use Silverlight in my normal Firefox installation. However when I use the High Security Mode it always tries to install Silverlight in the new user account. The installation seems to fail, causing the Pipelight installation wizard to stay open. Thus I always have to close the firejail process to get rid of the window, which is kind of annoying.
On another note, the same happened by just calling firejail firefox before I added the following items to my whitelist.
whitelist ~/.wine-pipelight whitelist ~/.wine-pipelight64 whitelist ~/.config/pipelight-widevine whitelist /etc/pipelight-widevine whitelist ~/.config/pipelight-silverlight5.1 whitelist /etc/pipelight-silverlight5.1@netblue30 commented on GitHub (Mar 5, 2016):
I'll add the whitelists to firefox profile, thanks!
@netblue30 commented on GitHub (Mar 6, 2016):
Fixed!