<div dir="ltr"><div class="gmail_default" style="font-size:large">Isn't that a wee bit, um, fascisitic of Mozilla? Shouldn't they at least make it user-controllable?<br><br></div><div class="gmail_default" style="font-size:large">Or perhaps they do. Otherwise, what would add-on developers do?<br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 10, 2015 at 5:11 PM, Jacob Hoffman-Andrews <span dir="ltr"><<a href="mailto:jsha@eff.org" target="_blank">jsha@eff.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FYI, Mozilla just announced they are planning to require all extensions<br>
be reviewed, approved, and signed by <a href="http://addons.mozilla.org" target="_blank">addons.mozilla.org</a> before they can<br>
be installed from a third party website:<br>
<br>
<a href="https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/" target="_blank">https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/</a><br>
<br>
We have already submitted HTTPS Everywhere to AMO, and are going through<br>
the (slow) review process, so this isn't a huge change for us. Hopefully<br>
the process to get a signature for a third party website is much faster<br>
than the process to upload a new version to AMO. Otherwise we will be<br>
faced with a very slow release process.<br>
_______________________________________________<br>
HTTPS-Everywhere mailing list<br>
<a href="mailto:HTTPS-Everywhere@lists.eff.org">HTTPS-Everywhere@lists.eff.org</a><br>
<a href="https://lists.eff.org/mailman/listinfo/https-everywhere" target="_blank">https://lists.eff.org/mailman/listinfo/https-everywhere</a><br>
</blockquote></div><br></div>