[meta] Don't allow any origins to send objects over WebChannel
Categories
(Toolkit :: General, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox132 | --- | fixed |
People
(Reporter: tcsc, Assigned: mccr8)
References
(Blocks 2 open bugs)
Details
(Keywords: meta)
Attachments
(1 file)
Updated•8 years ago
|
Updated•8 years ago
|
Updated•6 years ago
|
Comment 1•2 years ago
|
||
Hey Mark, all bugs tracked by this meta seems to be closed, can this also be closed?
Comment 2•2 years ago
|
||
Opened 3 more bugs which are required to finally remove this preference and capability.
Assignee | ||
Comment 3•3 months ago
|
||
There are only two URLs in the list now, https://content.cdn.mozilla.net
and https://install.mozilla.org
. As I rambled about a bit in bug 1786654, I can find no evidence that these sites exist any more, nor that they are used for WebChannels in any kind of way. Although I could not find any evidence that they were ever used so maybe I'm overlooking something. They don't even have DNS entries, so I think we can remove this entire mechanism.
Assignee | ||
Comment 4•3 months ago
|
||
I've been spending far too long staring at this code so I can put a patch together early next week, most likely.
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Comment 5•3 months ago
|
||
Updated•3 months ago
|
Assignee | ||
Comment 7•3 months ago
|
||
My patch changes two tests using weird objects instead of a string for the contentData property of the WebChannelMessageToChrome, simplifying the typing of this message.
Comment 9•2 months ago
|
||
bugherder |
Description
•