Closed
Bug 792309
Opened 13 years ago
Closed 11 years ago
Tracking bug for blocklisting support
Categories
(Marketplace Graveyard :: Security, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: ladamski, Unassigned)
References
Details
Tracking Marketplace work necessary to ensure support for blocklisting, which will be essentially limited to privileged apps for the 1.0 timeframe.
Updated•13 years ago
|
Component: Payments/Refunds → Security
Comment 1•13 years ago
|
||
This different than bug 773118?
Reporter | ||
Comment 2•13 years ago
|
||
Yes, 773118 is a corner case of this bug and as such a dependent.
Depends on: 773118
Comment 3•13 years ago
|
||
while I have this thought in my head:
when this is implemented the fake-updates proposed in bug 773117 will need to still work when the Marketplace listing is rejected or disabled (admin or user). (Normal updates would generally not be served when a listing is disabled, or the app is an unapproved state)
Reporter | ||
Comment 5•12 years ago
|
||
We still need a proper app blocklisting solution.
Flags: needinfo?(ladamski)
Comment 6•12 years ago
|
||
Can we assign this to an owner and give it a priority?
Comment 7•12 years ago
|
||
This is for hosted apps I assume?
One suggestion is to allow an app's origination store to have privileges to blocklist it, if the app came from a store. To use push notification to take an action on the installed app (for instance, remove it and set a notification message? or re-install the app to point to a hosted 'blocked' message). Or perhaps use a push message to Gaia to take an action on the device?
Comment 8•11 years ago
|
||
Closing this bug as there isn't actionable work. Please reopen/refile when there are things to do. Thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•