Skip to content

sandbox-permissions: Expand gvfs access #562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bbhtt merged 1 commit into from
Feb 4, 2025
Merged

sandbox-permissions: Expand gvfs access #562

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/sandbox-permissions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -424,6 +424,19 @@ Typical non-GNOME and non-GTK applications should use::
No application should be using ``--talk-name=org.gtk.vfs`` in its manifest, as
there are no D-Bus services named ``org.gtk.vfs``.

These permission grants the app, the ability to communicate with the
gvfs daemon and backends running on host. Depending on the backends
installed or running on host, it grants the ability to list mounted
devices (USB, optical etc.), detach/format/eject them, mount them
locally, read and write data. This is usually used with network storages
like WebDAV, Google Drive, SMB etc. but backends exist for MTP/PTP,
`USB <https://gitlab.gnome.org/GNOME/gvfs/-/tree/master/monitor/udisks2?ref_type=heads>_`,
special locations like ``trash://`` and the
`local filesystem <https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/daemon/gvfsbackendlocaltest.c?ref_type=heads>`_
too. So the app can access, read and write data from all of these
locations provided the daemon and backends are installed and running
on host.

External drive access
`````````````````````

Expand Down
Loading