The Mozilla Add-ons Blog has confirmed extension signing will be implemented in Firefox 40 for Android as well. Further, the ‘enforcement’ schedule will follow that of the desktop Firefox version. Automatic signing for Firefox for Android Add-ons hosted on AMO will begin soon.
Extension Signing
Read More
In many ways I hope I am wrong about this. Firefox is still a good browser (compared to Internet Explorer at least), but the Mozilla Developers continue to be indifferent towards the users. They have also deviated away from the original goals of keeping Firefox as small and lean as possible. In 2014, Firefox saw a drop in user base when the dramatic (and unwanted) user interface change known as Australia’s landed. Though most, if not all the changes made by this could be undone with The Classic Theme Restorer (CTR) add-on. Fastforward a year later and Mozilla Developers are still doing…
Like it or not, Extension Signing starts with Firefox 40 (coming August 2015). The Mozilla Wiki has quite a bit of information about extension signing. Signing will be done through addons.mozilla.org (AMO) and will be mandatory for all extensions, regardless of where they are hosted. Here is a timeline of when and how Extension Signing is going to be enforced: Firefox 40: Firefox warns about signatures but doesn’t enforce them. Firefox 41: Firefox will have a preference that allows signature enforcement to be disabled. Firefox 42: Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no…