[HTTPS-Everywhere] Firefox to require extensions be signed by addons.mozilla.org

[Bill Phillips]

Isn't that a wee bit, um, fascisitic of Mozilla? Shouldn't they at least
make it user-controllable?

Or perhaps they do. Otherwise, what would add-on developers do?



On Tue, Feb 10, 2015 at 5:11 PM, Jacob Hoffman-Andrews <jsha at eff.org> wrote:

> FYI, Mozilla just announced they are planning to require all extensions
> be reviewed, approved, and signed by addons.mozilla.org before they can
> be installed from a third party website:
>
>
> https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/
>
> We have already submitted HTTPS Everywhere to AMO, and are going through
> the (slow) review process, so this isn't a huge change for us. Hopefully
> the process to get a signature for a third party website is much faster
> than the process to upload a new version to AMO. Otherwise we will be
> faced with a very slow release process.
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20150210/0c8d7e85/attachment.html>