mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3465] Notification from Firefox add-on become of lower resolution & can not induced system sound notification. #2177
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#2177
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 @Nokia808 on GitHub (Jun 12, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3465
Hi dears.
I have on my Firefox 2 add-ons:
&
Without firejail, their text notification when appear at end of download appear with resolution seem to me the same of browser, & they induced sound notification of my Cinnamon DE. Cinnamon DE have option to associate a sound with system text notification so that every time a text system notification appear, there will be a sound induced. This option should activated by user ...
With firejail enabled for Firefox, the text notification appear but with lower resolution so that size of it & it's contents become larger. Also, they failed to induced system sound notification (audio notification).
Very clear this is due to affect of sandbox.
My request is ass following: if fixing this issue NOT undermine the security of firejail sandbox of Firefox, then this issue should fixed. Otherwise, if the fix lead to break security of sandbox then please do not fix it & kindly close this issue because it is cosmetic ...
@ghost commented on GitHub (Jun 12, 2020):
This sounds very much like a D-Bus issue, see the comments in /etc/firejail/firefox-common.profile. Assuming you are using 0.9.62, the comment on line 37 and following explains what you can try to fix this. The next release of firejail will have more finegrained dbus-* controls. But in 0.9.62 you don't have much other options than to allow D-Bus access. Have you tried adding
ignore nodbusto a firefox-common.local file yet? Additionally, depending on where the sound notification files are located on your OS, you might need to whitelist the relevant paths to those too.@rusty-snake commented on GitHub (Jun 12, 2020):
Native notifications are implemented over D-Bus (
org.freedesktop.Notifications) which need to be allowed.firejail <= 0.9.62:
https://github.com/netblue30/firejail/issues/2028#issuecomment-402754297
firejail >= 0.9.63:
You could allow
org.freedesktop.Notifications:3490ba4fe2/etc/profile-a-l/firefox.profile (L31-L35)Drawback: Under GNOME (and some other DEs) this allows to execute arbitrary code outside the sandbox, record the screen, ...
You can prevent this drawback with
However this looks terrible. A workaround could be a
.incfile for that, so that profiles only haveinclude dbus-notifications.inc. IMHO we should avoid to use a lot of inc-files only containing 2-3 lines. My purpose for that is #3412 (or alternative #3424).@Nokia808 commented on GitHub (Jun 12, 2020):
I think the best - if technically possible - to fix this WITHOUT break security or weakening the power of sandbox & make the fix built-in & user need nothing to do from heir/his side at all. Otherwise, the fix seem to me to penetrate the sandbox & this is bad ...