Closed
Bug 1501156
Opened 6 years ago
Closed 3 years ago
Push Notifications proactively leak data to Content Processes
Categories
(Core :: DOM: Push Subscriptions, enhancement, P3)
Core
DOM: Push Subscriptions
Tracking
()
RESOLVED
WORKSFORME
| Fission Milestone | Future |
People
(Reporter: tjr, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
In PContent, the Push* family of functions seem to broadcast Push Notification Data to all content processes, specifying a 'scope' and principal parameter that allows the Content Process to filter out what it is not responsible for. We should pre-filter these notifications so they are only delivered to the content process(es) that are authoritative for this scope/pricipal.
|
||
Updated•6 years ago
|
Priority: -- → P3
|
Reporter | |
Comment 1•6 years ago
|
||
This might be invalid given Bug 1199036
|
||
Comment 2•5 years ago
|
||
Do push notifications contain sensitive data?
Assuming for now that this bug is not a Fission MVP blocker.
Fission Milestone: --- → Future
|
|
Reporter | |
Comment 3•3 years ago
|
||
This doesn't seem to be an issue anymore; this is dead code that can be removed in Bug 1701328
|
|
Reporter | |
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•