How to Disable Signature Checking for Firefox Add-Ons

How can I disable signature checking for Firefox add-ons?

It is only possible to disable addons verification in Nightly and Developer channel. In other words it is not possible in Beta versions and standard releases.

1. Go to about:config (enter it into address bar)
2. Set xpinstall.signatures.required to false.

More at https://wiki.mozilla.org/Addons/Extension_Signing

How can I disable signature checking for Firefox add-ons?

It is only possible to disable addons verification in Nightly and Developer channel. In other words it is not possible in Beta versions and standard releases.

1. Go to about:config (enter it into address bar)
2. Set xpinstall.signatures.required to false.

More at https://wiki.mozilla.org/Addons/Extension_Signing

How to suppress the checking compatibility of add-ons dialog in Firefox with Selenium?

This dialog is shown only once whenever Firefox is updated. The reason it is shown each time for you is probably that Selenium creates a new profile each time. If you set extensions.lastAppVersion preference to "12.0" (or whatever the current Firefox version is) then Firefox will no longer think that it has been updated and won't show this dialog. However, it should be easier to add a extensions.showMismatchUI preference and set it to false, this will suppress this dialog (but not the other upgrade actions).

Side-note: extensions.checkCompatibility preference no longer does anything starting with Firefox 3.6, it is a version-specific preference in the current Firefox versions. So you would have to set extensions.checkCompatibility.12.0 preference instead. That disables compatibility checking for extensions completely however, not just the dialog you are concerned about.

How to sign Firefox addon after editing it?

The answer to your question's title can be found in the Mozilla wiki:

There it says:

How do I get my add-ons signed if they are not hosted on addons.mozilla.org (AMO)?

• You will need to create an AMO account and submit your add-on. There will be an option where you indicate the add-on won't be listed
  on AMO, and you'll be able to submit your add-on files without having
  them published on the site. Please read the Distribution Policy for
  more details.
• You can also use the jpm sign command to generate a signed XPI that can be self-hosted.
• There is an API you can use for signing.

Having said that, there are easier alternatives to signing the extension:

• Go to about:config and set xpinstall.signatures.required to false.
• Install the Nightly, Developer Edition or unbranded version of Firefox

Here's the related answer from the wiki:

What are my options if I want to install unsigned extensions in Firefox?

• The Developer Edition and Nightly versions of Firefox will have a setting to disable signature enforcement. There will also be
  special unbranded versions of Release and Beta that will have this
  setting, so that add-on developers can work on their add-ons without
  having to sign every build. To disable signature checks, you will need
  to set the xpinstall.signatures.required preference to "false".
  
  
  • type about:config into the URL bar in Firefox
  • in the Search box type xpinstall.signatures.required
  • double-click the preference, or right-click and selected "Toggle", to set it to false.

Regarding the question about getting rid of the warning regarding Strict Transport Security I see a few other possible solutions:

• Access your localhost via HTTP instead of HTTPS.
• Suppress sending the Strict-Transport-Security header on localhost.
• Install a proper certificate.

Note that this warning is shown for security purposes, so there is some risk in disabling it generally.

Firefox - locally modify addon and mandatory singing

https://wiki.mozilla.org/Add-ons/Extension_Signing#FAQ

• What are my options if I want to install unsigned extensions in
  Firefox?
  
  
  • The Developer Edition and Nightly versions of Firefox will have a setting to disable signature enforcement. There are also be special
    unbranded versions of Release and Beta that will have this setting
    (see , so that add-on developers can work on their add-ons without
    having to sign every build. To disable signature checks, you will need
    to set the xpinstall.signatures.required preference to "false".
    type about:config into the URL bar in Firefox
    in the Search box type xpinstall.signatures.required
    double-click the preference, or right-click and selected "Toggle", to set it to false.

Alternatively you can alter the addon's ID, make an AMO account and submit it for signing as unlisted addon which you can use for yourself.

---

Related Topics