github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #2323] Firefox Private Window allowing access to home entire folder in Kubuntu 18.04 #1549

New issue
Closed
opened 2026-05-05 08:12:40 -06:00 by gitea-mirror · 11 comments
gitea-mirror commented 2026-05-05 08:12:40 -06:00
Owner
Copy link

Originally created by @SuperSentient on GitHub (Dec 30, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2323

I just noticed that when Firefox is in a private window it allows access to the entire home folder. But this doesn't happen in a new/standard window, I'm using Firejail version 0.9.56. Using standard Firejail profile firejail firefox. But this doesn't happen with the Private Home profile.
Running Kubuntu 18.04.1

Originally created by @SuperSentient on GitHub (Dec 30, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2323 I just noticed that when Firefox is in a private window it allows access to the entire home folder. But this doesn't happen in a new/standard window, I'm using Firejail version 0.9.56. Using standard Firejail profile **firejail firefox**. But this doesn't happen with the Private Home profile. Running Kubuntu 18.04.1
gitea-mirror 2026-05-05 08:12:40 -06:00
gitea-mirror commented 2026-05-05 08:12:42 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Dec 30, 2018):

I cannot reproduce. Exact command used to run along with some output? and also how are you determining that Firefox can access everything?

<!-- gh-comment-id:450593510 --> @SkewedZeppelin commented on GitHub (Dec 30, 2018): I cannot reproduce. Exact command used to run along with some output? and also how are you determining that Firefox can access everything?
gitea-mirror commented 2026-05-05 08:12:42 -06:00
Author
Owner
Copy link

@SuperSentient commented on GitHub (Dec 31, 2018):

I cannot reproduce. Exact command used to run along with some output? and also how are you determining that Firefox can access everything?

When I try uploading a file to a website for example I can see the whole home folder. But I figured it out it happens when I right click over the panel icon for Firefox and chose either open in a new window or open in a new private window. But when I left click over the icon Firejail works normally. So right clicking either open in a new window or open in a new private window for some reason doesn't open Firefox in Firejail even though I have the icon configured to open Firefox in Firejail.

<!-- gh-comment-id:450596945 --> @SuperSentient commented on GitHub (Dec 31, 2018): > I cannot reproduce. Exact command used to run along with some output? and also how are you determining that Firefox can access everything? When I try uploading a file to a website for example I can see the whole home folder. But I figured it out it happens when I right click over the panel icon for Firefox and chose either open in a new window or open in a new private window. But when I left click over the icon Firejail works normally. So right clicking either open in a new window or open in a new private window for some reason doesn't open Firefox in Firejail even though I have the icon configured to open Firefox in Firejail.
gitea-mirror commented 2026-05-05 08:12:43 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Dec 31, 2018):

@SuperSentient which distro? which Desktop?

<!-- gh-comment-id:450641823 --> @rusty-snake commented on GitHub (Dec 31, 2018): @SuperSentient which distro? which Desktop?
gitea-mirror commented 2026-05-05 08:12:44 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Dec 31, 2018):

Please try this:

sudo ln -s /usr/bin/firejail /usr/local/bin/firefox

then close out of all firefox instances
then start firefox through your launcher

then try to reproduce this issue

<!-- gh-comment-id:450653309 --> @SkewedZeppelin commented on GitHub (Dec 31, 2018): Please try this: ``` sudo ln -s /usr/bin/firejail /usr/local/bin/firefox ``` then close out of all firefox instances then start firefox through your launcher then try to reproduce this issue
gitea-mirror commented 2026-05-05 08:12:44 -06:00
Author
Owner
Copy link

@SuperSentient commented on GitHub (Dec 31, 2018):

Please try this:

sudo ln -s /usr/bin/firejail /usr/local/bin/firefox

then close out of all firefox instances
then start firefox through your launcher

then try to reproduce this issue

Good thing I tried that command in Virtualbox because now I cant open Firefox outside of Firejail which is a problem for example if I want to export my Noscript's whitelist I cant export it to the desktop. :(

@ rusty-snake Its Kubuntu 18.04.1 KDE Plasma version 5.12.7 KDE Frameworks version 5.44.0 Qt version 5.9.5 Kernel version 4.15.0-43 generic.

<!-- gh-comment-id:450680870 --> @SuperSentient commented on GitHub (Dec 31, 2018): > Please try this: > > ``` > sudo ln -s /usr/bin/firejail /usr/local/bin/firefox > ``` > > then close out of all firefox instances > then start firefox through your launcher > > then try to reproduce this issue Good thing I tried that command in Virtualbox because now I cant open Firefox outside of Firejail which is a problem for example if I want to export my Noscript's whitelist I cant export it to the desktop. :( @ rusty-snake Its Kubuntu 18.04.1 KDE Plasma version 5.12.7 KDE Frameworks version 5.44.0 Qt version 5.9.5 Kernel version 4.15.0-43 generic.
gitea-mirror commented 2026-05-05 08:12:45 -06:00
Author
Owner
Copy link

@Fred-Barclay commented on GitHub (Dec 31, 2018):

Good thing I tried that command in Virtualbox because now I cant open Firefox outside of Firejail which is a problem for example if I want to export my Noscript's whitelist I cant export it to the desktop. :(

But can you reproduce the issue after you've run this? 😉 Basically we're trying to figure out if the problem is really with firejail or if it's just that KDE doesn't launch your customised firejail firefox command when you right-click the icon to launch. I suspect the latter option. If that's the case, the only way that I know of to make sure firefox always launches inside firejail is to first run the command @SkewedZeppelin provided. From then on, firefox will be configured to always launch inside firejail.

To revert the command, just remove the symlink and you'll be good to go:
sudo rm /usr/local/bin/firefox
(It's the same principle as firecfg).

<!-- gh-comment-id:450692154 --> @Fred-Barclay commented on GitHub (Dec 31, 2018): > Good thing I tried that command in Virtualbox because now I cant open Firefox outside of Firejail which is a problem for example if I want to export my Noscript's whitelist I cant export it to the desktop. :( But can you reproduce the issue after you've run this? :wink: Basically we're trying to figure out if the problem is really with firejail or if it's just that KDE doesn't launch your customised `firejail firefox` command when you right-click the icon to launch. I suspect the latter option. If that's the case, the only way **that I know of** to make sure firefox always launches inside firejail is to first run the command @SkewedZeppelin provided. From then on, firefox will be configured to always launch inside firejail. To revert the command, just remove the symlink and you'll be good to go: `sudo rm /usr/local/bin/firefox` (It's the same principle as `firecfg`).
gitea-mirror commented 2026-05-05 08:12:46 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jan 1, 2019):

[Desktop Entry]
…
Name=Firefox Web Browser
…
Exec=firefox %u
…
Actions=new-window;new-private-window;

[Desktop Action new-window]
Name=Open a New Window
…
Exec=firefox -new-window

[Desktop Action new-private-window]
Name=Open a New Private Window
…
Exec=firefox -private-window

@SuperSentient this is a shortened version of firefox.dektop, have you changed all three Exec lines or only the first one?

<!-- gh-comment-id:450721605 --> @rusty-snake commented on GitHub (Jan 1, 2019): ``` [Desktop Entry] … Name=Firefox Web Browser … Exec=firefox %u … Actions=new-window;new-private-window; [Desktop Action new-window] Name=Open a New Window … Exec=firefox -new-window [Desktop Action new-private-window] Name=Open a New Private Window … Exec=firefox -private-window ``` @SuperSentient this is a shortened version of `firefox.dektop`, have you changed all three `Exec` lines or only the first one?
gitea-mirror commented 2026-05-05 08:12:47 -06:00
Author
Owner
Copy link

@SuperSentient commented on GitHub (Jan 2, 2019):

[Desktop Entry]
…
Name=Firefox Web Browser
…
Exec=firefox %u
…
Actions=new-window;new-private-window;

[Desktop Action new-window]
Name=Open a New Window
…
Exec=firefox -new-window

[Desktop Action new-private-window]
Name=Open a New Private Window
…
Exec=firefox -private-window

@SuperSentient this is a shortened version of firefox.dektop, have you changed all three Exec lines or only the first one?

I didn't make any changes to Firejail I simply installed it and configured the icons to either firejail firefox or firejail --private-home=.mozilla firefox

<!-- gh-comment-id:450771676 --> @SuperSentient commented on GitHub (Jan 2, 2019): > ``` > [Desktop Entry] > … > Name=Firefox Web Browser > … > Exec=firefox %u > … > Actions=new-window;new-private-window; > > [Desktop Action new-window] > Name=Open a New Window > … > Exec=firefox -new-window > > [Desktop Action new-private-window] > Name=Open a New Private Window > … > Exec=firefox -private-window > ``` > > @SuperSentient this is a shortened version of `firefox.dektop`, have you changed all three `Exec` lines or only the first one? I didn't make any changes to Firejail I simply installed it and configured the icons to either **firejail firefox** or **firejail --private-home=.mozilla firefox**
gitea-mirror commented 2026-05-05 08:12:48 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Jan 2, 2019):

The recommended way to enable firejail for a program is through the symlink invocation feature. This is done by manually creating the symlink like shown above or by running firecfg --fix && sudo firecfg.
It is much more reliable and persistent compared to manually editing .desktop files/launchers/scripts.

If you really want to instead just edit the .desktop file:

cd ~/.local/share/applications;
mv firefox.desktop firefox.desktop.bak; #if you have an existing one
cp /usr/share/applications/firefox.desktop .;
sed -i 's/Exec=/Exec=firejail /' firefox.desktop; #include --private-home if you want
#optionally restart your DE
<!-- gh-comment-id:450774867 --> @SkewedZeppelin commented on GitHub (Jan 2, 2019): The recommended way to enable firejail for a program is through the symlink invocation feature. This is done by manually creating the symlink like shown above or by running `firecfg --fix && sudo firecfg`. It is much more reliable and persistent compared to manually editing .desktop files/launchers/scripts. If you really want to instead just edit the .desktop file: ```sh cd ~/.local/share/applications; mv firefox.desktop firefox.desktop.bak; #if you have an existing one cp /usr/share/applications/firefox.desktop .; sed -i 's/Exec=/Exec=firejail /' firefox.desktop; #include --private-home if you want #optionally restart your DE ```
gitea-mirror commented 2026-05-05 08:12:49 -06:00
Author
Owner
Copy link

@SuperSentient commented on GitHub (Jan 9, 2019):

The recommended way to enable firejail for a program is through the symlink invocation feature. This is done by manually creating the symlink like shown above or by running firecfg --fix && sudo firecfg.
It is much more reliable and persistent compared to manually editing .desktop files/launchers/scripts.

If you really want to instead just edit the .desktop file:

cd ~/.local/share/applications;
mv firefox.desktop firefox.desktop.bak; #if you have an existing one
cp /usr/share/applications/firefox.desktop .;
sed -i 's/Exec=/Exec=firejail /' firefox.desktop; #include --private-home if you want
#optionally restart your DE

No thanks I'll just launch Firefox by left clicking it, its not really a major issue for me.

<!-- gh-comment-id:452552719 --> @SuperSentient commented on GitHub (Jan 9, 2019): > The recommended way to enable firejail for a program is through the symlink invocation feature. This is done by manually creating the symlink like shown above or by running `firecfg --fix && sudo firecfg`. > It is much more reliable and persistent compared to manually editing .desktop files/launchers/scripts. > > If you really want to instead just edit the .desktop file: > > ```shell > cd ~/.local/share/applications; > mv firefox.desktop firefox.desktop.bak; #if you have an existing one > cp /usr/share/applications/firefox.desktop .; > sed -i 's/Exec=/Exec=firejail /' firefox.desktop; #include --private-home if you want > #optionally restart your DE > ``` No thanks I'll just launch Firefox by left clicking it, its not really a major issue for me.
gitea-mirror commented 2026-05-05 08:12:49 -06:00
Author
Owner
Copy link

@Fred-Barclay commented on GitHub (Jan 9, 2019):

Ok, closing then. Thanks! 😄

<!-- gh-comment-id:452566840 --> @Fred-Barclay commented on GitHub (Jan 9, 2019): Ok, closing then. Thanks! :smile:
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1549
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?