Commit eb50088f authored by Simon McVittie's avatar Simon McVittie Committed by Simon McVittie
parent d5fe0992
......@@ -215,9 +215,7 @@ not yet been defined.
The application bundle metadata should include simple, declarative
[permissions] which can be used to generate an AppArmor profile
in an automated way. Specific requirements for this have not yet
been defined; future work on this is tracked by [Apertis task
in an automated way. The [Permissions concept design] tracks this work.
#### Declaring system extensions
......@@ -575,7 +573,8 @@ requester's AppArmor label (part of the AppArmor context).
[Namespaces in XML]:
[Permissions concept design]:
[Security concept design]:
......@@ -546,6 +546,8 @@ have access to specific device capabilities, and even those that don't
should likely be informed when an application has access to their data
and services.
See the [Permissions concept design] for further details.
Application developers will declare the permissions their application
depends on in [application bundle metadata], and Apertis
will allow a user to approve a subset of an application's required
......@@ -2519,6 +2521,7 @@ This document references the following external sources of information:
[Application bundle metadata]:
[Application entry points]:
[Application layout]:
[Permissions concept design]:
[Public system extensions]:
This diff is collapsed.
......@@ -19,6 +19,7 @@
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