Add-ons/Extension Signing: Difference between revisions

Add-ons/Extension Signing (view source)

84 bytes added , 3 March 2016

Confirmed users

945

edits

@@ Line 11: / Line 11: @@
 * '''Firefox 40-42''': Firefox warns about signatures but doesn't enforce them.
 * '''Firefox 43''': Firefox has a preference that allows signature enforcement to be disabled (''xpinstall.signatures.required'' in about:config).
-* '''Firefox 46''': Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override.
+* '''Firefox 46''': Release and Beta versions of Firefox for Desktop will not allow unsigned extensions to be installed, with no override. Firefox for Android will enforce add-on signing, and will retain a preference to permit disabling of signing.
 The first ESR version to include signing support will be the Firefox ESR 45 release. Signing enforcement will be on by default, and can be disabled using the xpinstall.signatures.required preference.
-All Firefox extensions on AMO that have passed review are now signed.
+All Firefox extensions - for Desktop and Android - on AMO that have passed review are now signed.
 For unlisted (non-AMO) add-ons, submission and signing is active through [https://addons.mozilla.org AMO], and there is a [https://blog.mozilla.org/addons/2015/11/20/signing-api-now-available/ Signing API available] for automated submission and retrieval of unlisted addons.
-Firefox for Android auto-signing timelines is under discussion.
 == FAQ ==