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

[Russell Golden]

Yeah... It will kill doing so yourself. But it shouldn't affect HTTPS 
Everywhere.
... Come to think of it, I might have done the HTTPS Everywhere 
SeaMonkey stuff myself. I've done it for two extensions on AMO and for 
Xmarks. Can't remember if I did it for SeaMonkey or not.
*Grumble grumble reply all grumble* One of these days, I'll get used to 
this.

Ronnie wrote:
> Then this will kill converting firefox extensions to work with Seamonkey.
>
>
> Jacob Hoffman-Andrews 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
>>
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere