Commit e556569d authored by Emanuele Aina's avatar Emanuele Aina

canterbury-legacy-application-framework: More details on permissions

Be more explicit about how permissions where handled in Canterbury and fix the
link to the Permissions document which already provides details about Flatpak
in the context of the Apertis use-cases.
Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
parent c424c90c
......@@ -131,9 +131,15 @@ upstream technologies:
## Permissions
The permissions in the Apertis application framework are granted by the Flatpak
executable and are defined at build time. The original [permissions] description
already describes how Flatpak is handling the several cases.
No high level support for application permission has been implemented in Canterbury,
application access to resources was exclusively based on writing dedicated AppArmor
profiles for each applications can carefully reviewing them.
Flatpak instead lets application authors specify in the application manifest a
set of special high-level permissions. The Flatpak approach has been analysed
in more detail in the original [](permissions.md) document which already
described the use-cases for the permissions mechanism in the context of the
Apertis application framework.
## Preferences and persistence
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment