Sign our own extensions in Tor Browser
We should seriously look into signing our own extensions for Tor Browser 8. This includes the language packs we modify as well now (see: #26465 (moved)).
Activity
We at Tails currently patch the add-on signature checking code (on top of your current patch that adds a whitelist with
if (aAddon.id == […]aka. 0714762d25415271191503903a9f2fb0627ca38d on the tor-browser-60.1.0esr-8.0-1 branch) to add uBlock to the list. We've discussed this on the https://lists.torproject.org/pipermail/tbb-dev/2017-April/000515.html thread, where it seems that we (TBB team + Tails) reached a tentative agreement to move the whitelist to a pref. But so far we failed to write the corresponding code, sorry! FTR on Tails' side this is tracked on https://labs.riseup.net/code/issues/12571.It would be extremely helpful if the resolution for this ticket made things better for us (e.g. keep that patch and create a pref with the list of allowed unsigned add-ons, empty by default for TBB, where we would add uBlock) instead of worse. Things would get worse for us if the code that adds a whitelist with
if (aAddon.id == […]was fully removed: then we would need to carry it as part of Tails delta, which is quite ugly and painful.
Trac:
Username: CyrilBrulebois
Cc: intrigeri, dmr to intrigeri, dmr, ckb@riseup.net-
Trac:
Username: hefee
Cc: intrigeri, dmr, ckb@riseup.net to intrigeri, dmr, ckb@riseup.net, hefee
