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 #6547] Fine-grained permission to DBus for Dropbox Profile. #3299

New issue
Closed
opened 2026-05-05 09:53:57 -06:00 by gitea-mirror · 0 comments
gitea-mirror commented 2026-05-05 09:53:57 -06:00
Owner
Copy link

Originally created by @amidukr on GitHub (Nov 17, 2024).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6547

Hi,

I was reviewing Dropbox profile bundled together with firejail recently, and it doesn't has granular permissions for DBus, it seems that by default dbus is open for all. Actually impact is well described here:
https://github.com/netblue30/firejail/wiki/Restrict-DBus

I've tried to update a little bit the profile, and I've found out a way how to log dbus communication, however I've confused about certain aspect.

According to DBus communication log, I see that this messages are filtered, and it really numerous of them.

dropbox.dbus.log|6 col 1-23| Filtering message due to arg0 org.a11y.Bus, policy: 0 (required 1)
dropbox.dbus.log|10 col 1-23| Filtering message due to arg0 org.freedesktop.Notifications, policy: 0 (required 1)
dropbox.dbus.log|20 col 1-23| Filtering message due to arg0 org.kde.StatusNotifierWatcher, policy: 0 (required 1)
dropbox.dbus.log|61 col 1-23| Filtering message due to arg0 org.gtk.vfs.Daemon, policy: 0 (required 2)
dropbox.dbus.log|67 col 1-23| Filtering message due to arg0 org.gtk.vfs.Daemon, policy: 0 (required 1)
dropbox.dbus.log|90 col 1-23| Filtering message due to arg0 org.gtk.Settings, policy: 0 (required 1)
dropbox.dbus.log|94 col 1-23| Filtering message due to arg0 org.gtk.Settings, policy: 0 (required 2)
dropbox.dbus.log|98 col 1-23| Filtering message due to arg0 org.kde.StatusNotifierWatcher, policy: 0 (required 1)
dropbox.dbus.log|114 col 1-23| Filtering message due to arg0 org.gtk.Settings, policy: 0 (required 1)
dropbox.dbus.log|123 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1)
dropbox.dbus.log|127 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 2)
dropbox.dbus.log|137 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1)
dropbox.dbus.log|165 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1)
dropbox.dbus.log|169 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 2)
dropbox.dbus.log|179 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1)

However when I've checked flatpak, how they doing it permissions through flatseal, I can see only two dbus names enabled for dropbox, while firejail dbus log has much more messages filtered.

image

  1. Also I am not really understanding this flatpak wildcard. Is it really secure to declare ownership for such global namespace in dbus?
  2. How could I know from dbus log, which dbus names should I open for ownership?
  3. Do I need to open all this message from above for dbus talks, or I just need to open only two messages like flatpak doing?
    3.1 Still curious about principle, why flatpak skipping so many dbus names for dropbox?

BTW: I can test it on my local and make Pull Request for dropbox profile if needed, to have fine-grained permissions for dropbox.

Originally created by @amidukr on GitHub (Nov 17, 2024). Original GitHub issue: https://github.com/netblue30/firejail/issues/6547 Hi, I was reviewing Dropbox profile bundled together with firejail recently, and it doesn't has granular permissions for DBus, it seems that by default dbus is open for all. Actually impact is well described here: https://github.com/netblue30/firejail/wiki/Restrict-DBus I've tried to update a little bit the profile, and I've found out a way how to log dbus communication, however I've confused about certain aspect. According to DBus communication log, I see that this messages are filtered, and it really numerous of them. ``` dropbox.dbus.log|6 col 1-23| Filtering message due to arg0 org.a11y.Bus, policy: 0 (required 1) dropbox.dbus.log|10 col 1-23| Filtering message due to arg0 org.freedesktop.Notifications, policy: 0 (required 1) dropbox.dbus.log|20 col 1-23| Filtering message due to arg0 org.kde.StatusNotifierWatcher, policy: 0 (required 1) dropbox.dbus.log|61 col 1-23| Filtering message due to arg0 org.gtk.vfs.Daemon, policy: 0 (required 2) dropbox.dbus.log|67 col 1-23| Filtering message due to arg0 org.gtk.vfs.Daemon, policy: 0 (required 1) dropbox.dbus.log|90 col 1-23| Filtering message due to arg0 org.gtk.Settings, policy: 0 (required 1) dropbox.dbus.log|94 col 1-23| Filtering message due to arg0 org.gtk.Settings, policy: 0 (required 2) dropbox.dbus.log|98 col 1-23| Filtering message due to arg0 org.kde.StatusNotifierWatcher, policy: 0 (required 1) dropbox.dbus.log|114 col 1-23| Filtering message due to arg0 org.gtk.Settings, policy: 0 (required 1) dropbox.dbus.log|123 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1) dropbox.dbus.log|127 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 2) dropbox.dbus.log|137 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1) dropbox.dbus.log|165 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1) dropbox.dbus.log|169 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 2) dropbox.dbus.log|179 col 1-23| Filtering message due to arg0 org.gnome.Shell.Extensions, policy: 0 (required 1) ``` However when I've checked flatpak, how they doing it permissions through flatseal, I can see only two dbus names enabled for dropbox, while firejail dbus log has much more messages filtered. ![image](https://github.com/user-attachments/assets/708b4304-3c19-4a1d-a973-9137a27f3053) 1. Also I am not really understanding this flatpak wildcard. Is it really secure to declare ownership for such global namespace in dbus? 2. How could I know from dbus log, which dbus names should I open for ownership? 3. Do I need to open all this message from above for dbus talks, or I just need to open only two messages like flatpak doing? 3.1 Still curious about principle, why flatpak skipping so many dbus names for dropbox? BTW: I can test it on my local and make Pull Request for dropbox profile if needed, to have fine-grained permissions for dropbox.
gitea-mirror 2026-05-05 09:53:57 -06:00
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#3299
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?