Closed AntoineTurmel closed 8 years ago
I wonder if this issue should not be revised (and maybe planned), according to current schedule, cf. link mentioned in issue #29:
Firefox 41 [2015-09-22]: Unsigned extensions will be disabled by default [...] Firefox 42 [2015-11-03]: The Beta and Release versions [...] will remove the preference that allows unsigned extensions to be installed [...]
At least we need #14
If I understood correctly, Mozilla seems to want deferring the signing enforcement for extensions. See Mozilla postpones Firefox add-on signing enforcement on gHacks and Turn off signing requirements in Firefox 41 and 42 on Bugzilla@Mozilla for further details.
Publishing in AMO #3 will sign add-on transparently
Signing it is no longer a problem ;)
Just to add link to a recent news about signing: https://blog.mozilla.org/addons/2015/12/18/signing-firefox-add-ons-with-jpm-sign/ Interesting!
See: https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/