canmove, Confirmed users
1,220
edits
FirefoxOS/New security model/Packaging: Difference between revisions
Jump to navigation
Jump to search
FirefoxOS/New security model/Packaging (view source)
Revision as of 15:14, 22 July 2015
, 22 July 2015no edit summary
Ptheriault (talk | contribs) |
Ptheriault (talk | contribs) No edit summary |
||
| Line 58: | Line 58: | ||
... | ... | ||
== | == Manifest Requirements == | ||
==='' name'' === | ==='' name'' === | ||
| Line 102: | Line 102: | ||
*Question: Do ALL resources need to live INSIDE the package? If we support arbitrary loads this would allow support for non-packaged privileged apps too, but I don't know what complexity this would add to the loading/verification process. | *Question: Do ALL resources need to live INSIDE the package? If we support arbitrary loads this would allow support for non-packaged privileged apps too, but I don't know what complexity this would add to the loading/verification process. | ||
=== ''package-origin''=== | === ''package-origin??''=== | ||
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. | 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''=== | |||
We need the permissions of the signed package so in order to know what permissions to grant to the new process. | |||
== Processing Model == | == Processing Model == | ||