Backport JS Poison Patch

https://bugzilla.mozilla.org/show_bug.cgi?id=981991

This will make reading a freed object crash instead of succeeding.

Trac:
Parent Ticket: #28707 (moved)

added GeorgKoppen201903 TorBrowserTeam201903 component::applications/tor browser ff68-esr-will-have owner::tbb-team parent::28707 priority::medium resolution::fixed severity::normal sponsor::44-can status::closed tbb-security type::enhancement labels

Trac:
Owner: N/A to tbb-team
Component: - Select a component to Applications/Tor Browser

Trac:
Type: defect to enhancement
Keywords: N/A deleted, TorBrowserTeam201901, tbb-security added

Moving tickets to February.

Trac:
Keywords: TorBrowserTeam201901 deleted, TorBrowserTeam201902 added

Trac:
Keywords: N/A deleted, GeorgKoppen201902 added

Moving my tickets to March.

Trac:
Keywords: TorBrowserTeam201902 deleted, TorBrowserTeam201903 added

Now for my keyword.

Trac:
Keywords: GeorgKoppen201902 deleted, GeorgKoppen201903 added

Tickets on our radar for 8.5

Trac:
Keywords: N/A deleted, tbb-8.5 added

It seems we want to have at least https://bugzilla.mozilla.org/show_bug.cgi?id=1415852 as well for AlwaysPoison(). This gets slightly more complicated than I had hoped. Thus, I am not sure whether we should actually backport that ourselves. I guess really cool would be an esr60 patch Mozilla folks working on those bugs do like.

Whatever we do in the meantime we'll get this with ff68-esr

Trac:
Keywords: tbb-8.5 deleted, ff68-esr-will-have added

Adding Sponsor 44 to ESR68 tickets

Trac:
Sponsor: N/A to Sponsor44-can

9.0a6, which is about to get built, is based on ESR 68, so closing.

Trac:
Resolution: N/A to fixed
Status: new to closed

closed

moved to tpo/applications/tor-browser#29049 (closed)