mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1584] Firefox Nightly breaks out of firejail(-0.9.50,-0.9.51) #1055
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#1055
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 (Oct 1, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1584
Hi,
I've installed firejail from AUR(firejail-git) and downloaded firefox nightly(58.0a1). I've created a directory
FF_Nightlythen moved the firefox directory there. When I start it asfirejail --private=${HOME}/FF_Nightly ./firefox/firefox, Firefox 55.0(the installed one) will start instead of Nightly - and it's using the configuration from another running sandbox. The same happens when I simply start FFN but I thought firejail would stop it. I have two FF sandboxes with their own config but when I start FFN it'll start with the latest sandbox's config. It seems like FFN breaks out of the jail somehow.@ghost commented on GitHub (Oct 1, 2017):
This broke my old configurations - when I start them they glitch and show black and white rectangles.
Edit: this is my fault: I've set
read-only /devglobally.@SkewedZeppelin commented on GitHub (Oct 1, 2017):
See #939
@ghost commented on GitHub (Oct 1, 2017):
@SpotComms I can run two different instances of firefox in different sandboxes - I use them now and they both look and behave differently. The problem is with FFN - I've made a different jail for it and it could access the others' content.
@SkewedZeppelin commented on GitHub (Oct 1, 2017):
So I just tested this
Even with a new network namespace and ipc-namespace, it still launches a window in the first.
However simply adding
-no-remotewill allow running multiple instances of both firefox and firefox-nightly at the same time. Also in that case even though it works I think it might still be possible to get back into the context of the other running Firefox instances.Can you give that a go?
Edit: See #1570, #784, #330
@ghost commented on GitHub (Oct 1, 2017):
@SpotComms You've missed the
--private=${HOME}/FF_Nightlypart.Edit: also, -no-remote does work.