Canmove, confirm
1,220
edits
Changes
→Draft Specification
# Permissions should be enforced regardless of version of B2G installed
== Draft Specification Summary ==
===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 chooses 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===
#By default all Web Apps have the no special permissions, the same as any other web page.
#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)
#An App Store can grant permissions to a Web App during the install process (but not necessarily all of the requested permissions
#The user’s default permission policy is applied to the requested permissions (see permissions management) and requested permissions are updated
#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.
===Default Permission Policy===
Each B2G device comes with has a default permissions policy, which overrides the permissions granted, by takes precedence over the app store. This is expected to ensure some contain rules for a subset of permissions can never be granted above a certain level – . Its purpose is:- for example, a device manufacturers to set safe default setting limits for permissions- for location might be that even apps, which are granted access users to location, must always ask the user. This could modify this policy to be more strict, and globally deny applications from accessing location information.decide on global limits for permissions
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.
A user should be warned before they override the Default Permission Policy
===Permission Types===
For privacy-related permissions, the user must always be asked, unless they have overridden
Permission cases:
Deny
Prompt (default to remember)
Prompt (default not to remember)
Allow
====Trust Model====
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.
===Security Requirements for Critical App Deployment===
Still under heavy discussion. (Trusted Stores, Code Signing etc)
* Which permissions will be classed as sensitive
* what will the minimum bar be
* Will there even be a separate set of requirements, or will threats be mitigated by App Store processes instead?
== Proposals ==
