FirefoxOS/New security model/Packaging: Difference between revisions

FirefoxOS/New security model/Packaging (view source)

12 bytes added , 23 July 2015

canmove, Confirmed users

1,220

edits

@@ Line 59: / Line 59: @@
 ==  Manifest Requirements ==
+==='' uuid'' ===
+Signed packages must contain a uuid (ACTUAL NAME TBD) field. The unique identifier for a signed package is the tuple of the package origin and the app name. (e.g. foo.com!uuid). NOTE: Marketplace might supply this.
+=== ''permissions''===
+We need the permissions of the signed package so in order to know what permissions to grant to the new process.
 === ''Resources''===
 We add a ''resources'' section to the app manifest which enumerates content which needs to have integrity check. All resources are specified by relative URIs and meaning they must reside inside the package.
-==='' uuid'' ===
-Signed packages must contain a uuid (ACTUAL NAME TBD) field. The unique identifier for a signed package is the tuple of the package origin and the app name. (e.g. foo.com!uuid). NOTE: Marketplace might supply this.
 === ''package-location''===
 We need a field in the manifest which specifies the origin for where the package is allowed to be hosted. This needs to be checked by gecko when a package is loaded to ensure that the package hasn't been moved and re-hosted.
-=== ''permissions''===
+=== Example ===
-We need the permissions of the signed package so in order to know what permissions to grant to the new process.
   {
   "UUID": "some-uuid",