[FR] sandboxing functionality

[Samueru-sama]

It is actually not that hard of a feature, specially if you use this tool which already greatly simplifies it.

Basically the symlink to the appimage in XDG_BIN_HOME would have to be replaced for a wrapper script that calls sas and passes the configured locations to be added.

In AM we provide the following locations to be configured:

Basically XDG_DOCUMENTS_DIR, XDG_DOWNLOAD_DIR, XDG_MUSIC_DIR, etc ,etc + a single manual override.

[kem-a]

This is shell script, it works great in terminal. To implement this in app you will need an API and written in C or similar low level language. Integration in GUI will be very trivial. Will need entire permission management window with widgets, toggles also popup dialogs with hooks when app tries to access restricted location that would allow user interaction, like allow/deny. Not a simple feat

[Samueru-sama]

To implement this in app you will need an API and written in C or similar low level language.

Check how flatpak, glycin, webkit2gtk use bubblewrap, because I don't think there is such API, they just set a ton of flags for it.

Will need entire permission management window with widgets, toggles

All you need is toggles for the following locations, these are options for the --add-file flag in sas:

xdg-desktop
xdg-documents
xdg-download
xdg-music
xdg-pictures
xdg-publicshare
xdg-templates
xdg-videos

Optionally I also support the following locations not found in the base dir spec:

xdg-applications
xdg-games

Passing these locations alone gives read only access, adding :rw to the end gives write access.

So basically the user would have some toggles for these locations in the GUI, if they allow them, then you would write to a config file the allowed locations or just directly add the allowed locations to the wrapper script in XDG_BIN_HOME, which would look like this:

#!/bin/sh
sas --trust-once \
  --add-dir xdg-download:rw \
  --add-dir xdg-desktop \
  -- /path/to/target/appimage "$@"

also popup dialogs with hooks when app tries to access restricted location that would allow user interaction, like allow/deny. Not a simple feat

This handled by the portals which already work in this sandbox.