Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avatar for Username

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Unbranded build disabled my add-on (ublock) because of expired CA TLS cert, shouldn't have.

  • No replies
  • 0 have this problem
  • 146 views
mozilla706
mozilla706

Well, it's happened. I am using the unbranded build specifically so that I do not have to have signed or verified extensions. But tonight my browser broke anyway because of the expiring CA TLS certs for the add-ons repository.

"One or more installed add-ons cannot be verified and have been disabled [Learn More]". If I click the [Learn More] button nothing happens. It just disappears.

And when I check: "uBlock Origin could not be verified for use in Nightly and has been disabled."

This should not be happening in the unbranded builds. I imagine it is happening in the custom Debian esr too. They're supposed to allow unsigned/unverified extensions/add-ons but now this apparently bug is happening.

To be clear, this was expected for normal Firefox releases with all normal extension signing stuff. But that was explicitly not supposed to be required for the unbranded builds. And so this is a bug.

Well, it's happened. I am using the unbranded build specifically so that I do not have to have signed or verified extensions. But tonight my browser broke anyway because of the expiring CA TLS certs for the add-ons repository. "One or more installed add-ons cannot be verified and have been disabled [Learn More]". If I click the [Learn More] button nothing happens. It just disappears. And when I check: "uBlock Origin could not be verified for use in Nightly and has been disabled." This should not be happening in the unbranded builds. I imagine it is happening in the custom Debian esr too. They're supposed to allow unsigned/unverified extensions/add-ons but now this apparently bug is happening. To be clear, this was expected for normal Firefox releases with all normal extension signing stuff. But that was explicitly not supposed to be required for the unbranded builds. And so this is a bug.

Chosen solution

Nevermind. Completely user error. I was so sure I had xpinstall.signatures.required false because I regularly add my own and edit other's add-ons without going through the signing portal in unbranded. But... apparently not. After toggling it back false again everything works in unbranded. Sorry.

For those using officially branded Firefox (not unbranded where about:config changes actually work) someone found the actual problem and how it can be fixed in both pre-existing Firefox installs and future Firefox releases, https://rentry.org/disableaddonsigning

Basically, unpacking omni.ja and editing the code therein.

In AppConstants.jsm, I've changed from true MOZ_REQUIRE_SIGNING: //@line 287 "$SRCDIR/toolkit/modules/AppConstants.jsm" false, //@line 291 "$SRCDIR/toolkit/modules/AppConstants.jsm"

to false, MOZ_ALLOW_ADDON_SIDELOAD: to true

in modules\addons\XPIDatabase.json: /**

  • Returns true if signing is required for the given add-on type.
  • @Param {string} aType
  • The add-on type to check.
  • @returns {boolean}
  • /

mustSign(aType) { return false;

Read this answer in context 👍 0

All Replies (1)

mozilla706
mozilla706 Question owner

Chosen Solution

Nevermind. Completely user error. I was so sure I had xpinstall.signatures.required false because I regularly add my own and edit other's add-ons without going through the signing portal in unbranded. But... apparently not. After toggling it back false again everything works in unbranded. Sorry.

For those using officially branded Firefox (not unbranded where about:config changes actually work) someone found the actual problem and how it can be fixed in both pre-existing Firefox installs and future Firefox releases, https://rentry.org/disableaddonsigning

Basically, unpacking omni.ja and editing the code therein.

In AppConstants.jsm, I've changed from true MOZ_REQUIRE_SIGNING: //@line 287 "$SRCDIR/toolkit/modules/AppConstants.jsm" false, //@line 291 "$SRCDIR/toolkit/modules/AppConstants.jsm"

to false, MOZ_ALLOW_ADDON_SIDELOAD: to true

in modules\addons\XPIDatabase.json: /**

  • Returns true if signing is required for the given add-on type.
  • @Param {string} aType
  • The add-on type to check.
  • @returns {boolean}
  • /

mustSign(aType) { return false;

Modified by mozilla706

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.