Canmove, confirm
1,220
edits
Changes
no edit summary
=== Enforcement of permissions on device ===
# Permissions should be enforced regardless of version of B2G installed
== Draft Specification ==
===Core Principles===
#User control: Users control what application permissions an application has at all times (pre, during and post installation).
#Secure by default: A user who choses to accept the default permissions recommended by a store must be secure by default
#Least Privilege: Applications must be granted the minimum privileges necessary to function
#Minimize Permissions: APIs should be designed in such a way to provide the most functionality without the need to be granted permissions
===Process for granting permissions===
1. By default all Web Apps have the no special permissions, the same as any other web page.
2. A Web App requests permissions in the manifest when submitting to a store (an application may only be granted permissions that it requests in the manifest)
3. An App Store can grant permissions to a Web App during the install process (but not necessarily all of the requested permissions
4. The user’s default permission policy is applied to the requested permissions (see permissions management) and requested permissions are updated
5. The user is informed of the permissions during installation, and can modify them if desired, or choose to trust the defaults set by the App Store.
Note: If sensitive permissions are requested, certain security requirements may be placed on the application.
===Default Permission Policy===
Each B2G device comes with a default permissions policy, which overrides the permissions granted, by the app store. This is to ensure some permissions can never be granted above a certain level – for example, a default setting for location might be that even apps, which are granted access to location, must always ask the user. This could modify this policy to be more strict, and globally deny applications from accessing location information.
===Permission Types===
For privacy-related permissions, the user must always be asked, unless they have overridden
Deny
Prompt (default to remember)
Prompt (default not to remember)
Allow
====Management of Permissions====
A user can modify the permissions granted to a Web App at any time including granting or revoking privileges
Permissions can be granted per application, or set globally for all applications
Users need to be guided on the consequence of changing permissions, and protected from making choices which are insecure or which could disable their device (e.g. removing the permissions setting capability from the permissions web app)
Permissions can be modified either through a permission manager application, or set through contextual actions (e.g. response to security prompts or through behavior
====Trust Model====
The user is the root source of trust for permissions settings.
B2G devices will be shipped with a root Trusted Store which has the power to set the permissions defaults for an Web App.
The user can choose to override these permissions (either granting or revoking privileges), but by default the permissions should be safe for the user, and represent the minimum permissions the application needs to run.
== Proposals ==
