Closed
Bug 768881
Opened 12 years ago
Closed 12 years ago
Update manifest to reflect that permissions can be implicit or explicit
Categories
(Web Apps :: General, defect)
Tracking
(blocking-kilimanjaro:?, blocking-basecamp:+)
RESOLVED
DUPLICATE
of bug 772358
People
(Reporter: ladamski, Unassigned)
Details
Some permissions can be granted automatically for an application type (implicit), while other, high-risk privileges need to be approved by the user (explicit).
Currently the only field in the manifest spec (http://mozilla.github.com/webapps-spec/) is "required_features", which is insufficient. We can either add "optional_features" to the manifest, or replace "required_features" with simply a list of requested "permissions".
Reporter | ||
Updated•12 years ago
|
Blocks: 768862
Group: webtools-security
Summary: Permissions should be grouped into implicit or explicit → Update manifest to reflect that permissions can be implicit or explicit
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: --- → ?
Updated•12 years ago
|
blocking-kilimanjaro: --- → ?
Reporter | ||
Comment 1•12 years ago
|
||
Note that only permissions enumerated in the manifest should be available to an application. This holds true whether they are implicit or explicit permissions.
I don't think we want to use the "required_features" part. That is designed to enumerate the platform capabilities that the app needs in order to show up in the app store. For example that the app needs a specific screen size, or for the runtime to implement DOM4 Core.
I filed bug 772358 on an explicit new manifest property which just enumerates security aspects.
With that I think we should WONTFIX this bug.
Reporter | ||
Comment 3•12 years ago
|
||
I don't think we should use "required_features" either. The gist of this bug was that we should enumerate permissions in the manifest. The key question is I guess whether we want to have separate groups of explicit vs implicit permissions or have them all in one list. After giving it more thought, I'm inclined to go with the latter.
Updated•12 years ago
|
blocking-basecamp: ? → +
You need to log in
before you can comment on or make changes to this bug.
Description
•