177
edits
Apps/Security/Enforcement: Difference between revisions
Jump to navigation
Jump to search
→Requirements
(Created page with "= Application Permissions Enforcement = This section defines how permissions are to be enforced at the Operating System (kernel) level. B2G is defined as a "full Operating Syst...") |
|||
| Line 4: | Line 4: | ||
== Requirements == | == Requirements == | ||
* It must not be possible for any one binary executable being compromised to result in a total systems and security failure. | |||
** Compromise of the main B2G executable must not result in complete control of the device (e.g. dialer, GPS, camera) | |||
** Compromise of an individual component (e.g. GPS) must not result in any other area (dialer, camera, main UI) being compromised | |||
* Application Developers should be presented with easy bullet-point style permission sets that can be applied to their application. | |||
** These should map easily onto the enforcement within the underlying OS security model | |||
== Proposals == | == Proposals == | ||