X
Tap here to go to the mobile version of the site.

Support Forum

Is a signed add-on *permanently* allowed?

Posted

The new rules allowing only signed add-ons make me nervous, since an add-on I depended upon so heavily, and had spent a great amount of time configuring -- Menu Editor -- suddenly became unusable when I updated to Firefox 43, as Menu Editor is unsigned. There was no warning before the update that signing would suddenly switch from "recommended" to strictly enforced as of that update. I have since learned of the about:config workaround to re-enable it (which at least allows me to restore the Menu Editor functionality while I seek and configure a signed alternative), but I understand that this workaround will be unavailable in versions 44+. And that once an add-on is disabled due to being unsigned, reverting to an older version of Firefox (or doing a Windows System Restore) will *not* re-enable it.

My concern going forward, and my question, is whether or not -- even if I am using only signed add-ons, -- my ability to use one or more of them will go away if its signing/signature expires, or is not renewed. Or is a given add-on *permanently* permitted after the original signing (for as long as it remains compatible with future Firefox versions, anyway)?

The new rules allowing only signed add-ons make me nervous, since an add-on I depended upon so heavily, and had spent a great amount of time configuring -- Menu Editor -- suddenly became unusable when I updated to Firefox 43, as Menu Editor is unsigned. There was no warning before the update that signing would suddenly switch from "recommended" to strictly enforced as of that update. I have since learned of the about:config workaround to re-enable it (which at least allows me to restore the Menu Editor functionality while I seek and configure a signed alternative), but I understand that this workaround will be unavailable in versions 44+. And that once an add-on is disabled due to being unsigned, reverting to an older version of Firefox (or doing a Windows System Restore) will *not* re-enable it. My concern going forward, and my question, is whether or not -- even if I am using only signed add-ons, -- my ability to use one or more of them will go away if its signing/signature expires, or is not renewed. Or is a given add-on *permanently* permitted after the original signing (for as long as it remains compatible with future Firefox versions, anyway)?

Chosen solution

It looks like Menu Editor has been pulled from the Addons website. https://addons.mozilla.org/en-US/firefox/addon/menu-editor/

I have been using Menu Wizard for awhile. I find to be a suitable replacement for Menu Editor. https://addons.mozilla.org/en-US/firefox/addon/s3menu-wizard/

There's no expiration date on signing. Once an add-on that is hosted at AMO, all updates in the future will be signed automatically. 3rd party hosted extensions might be a different story, though.

Read this answer in context 0

Additional System Details

Installed Plug-ins

  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • Shockwave Flash 20.0 r0

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0

More Information

the-edmeister
  • Top 25 Contributor
  • Moderator
5395 solutions 40084 answers

Chosen Solution

It looks like Menu Editor has been pulled from the Addons website. https://addons.mozilla.org/en-US/firefox/addon/menu-editor/

I have been using Menu Wizard for awhile. I find to be a suitable replacement for Menu Editor. https://addons.mozilla.org/en-US/firefox/addon/s3menu-wizard/

There's no expiration date on signing. Once an add-on that is hosted at AMO, all updates in the future will be signed automatically. 3rd party hosted extensions might be a different story, though.

It looks like Menu Editor has been pulled from the Addons website. https://addons.mozilla.org/en-US/firefox/addon/menu-editor/ I have been using Menu Wizard for awhile. I find to be a suitable replacement for Menu Editor. https://addons.mozilla.org/en-US/firefox/addon/s3menu-wizard/ There's no expiration date on signing. Once an add-on that is hosted at AMO, all updates in the future will be signed automatically. 3rd party hosted extensions might be a different story, though.
ideato 893 solutions 6250 answers

Hello

Rick216 said

...... but I understand that this workaround will be unavailable in versions 44+.........

It is 47+ now (*)

thank you

Hello ''Rick216 [[#question-1104871|said]]'' <blockquote> ...... but I understand that this workaround will be unavailable in versions 44+......... </blockquote> It is 47+ now ([https://wiki.mozilla.org/Firefox/AddOns/Status/Updates *]) thank you

Question owner

Thank you both for the quick answers and very helpful info.

Thank you both for the quick answers and very helpful info.
ideato 893 solutions 6250 answers

Update :

Firefox 46: Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override.

https://wiki.mozilla.org/Addons/Extension_Signing#Timeline

https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/

'''Update''' : Firefox '''46''': Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override. https://wiki.mozilla.org/Addons/Extension_Signing#Timeline https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/

Question owner

ideato said

Update : Firefox 46: Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override. https://wiki.mozilla.org/Addons/Extension_Signing#Timeline https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/

Thanks for the update! Can't say I understand how these decisions are made, but I'm surprised Mozilla would specify that removal of the signing enforcement workaround would be delayed to 47+ but then move that up to 46. Regardless I'm glad I now have further incentive not to procrastinate preparing for the switch.

''ideato [[#answer-834849|said]]'' <blockquote> '''Update''' : Firefox '''46''': Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override. https://wiki.mozilla.org/Addons/Extension_Signing#Timeline https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/ </blockquote> Thanks for the update! Can't say I understand how these decisions are made, but I'm surprised Mozilla would specify that removal of the signing enforcement workaround would be delayed to 47+ but then move that up to 46. Regardless I'm glad I now have further incentive not to procrastinate preparing for the switch.

Modified by Rick216

the-edmeister
  • Top 25 Contributor
  • Moderator
5395 solutions 40084 answers

Firefox 47 was just a proposal by the Add-on Team for pushing back that pref, and wasn't decided until Jan 22nd as being Firefox 46 as announced in that blog.

Firefox '''47''' was just a proposal by the Add-on Team for pushing back that pref, and wasn't decided until Jan 22nd as being '''Firefox 46''' as announced in that blog.