Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Søg i Support

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.

Læs mere

Unbranded Builds

  • 6 svar
  • 3 har dette problem
  • 5 visninger
  • Seneste svar af moz101mo

more options

Hello,

I understand that setting "xpinstall.signatures.required" to false has no effect in FF 47. I'd appreciate any information regarding the unbranded builds.

Best regards.

Hello, I understand that setting "xpinstall.signatures.required" to false has no effect in FF 47. I'd appreciate any information regarding the unbranded builds. Best regards.

Ændret af Yaron den

Valgt løsning

yes i'm fairly sure about this. there was a chanage of plans about this recently - addon signing will only be enforced once those unbranded builds are fully available & that's targeted for firefox 48 for now. https://wiki.mozilla.org/Addons/Extension_Signing#Timeline

Læs dette svar i sammenhæng 👍 1

Alle svar (6)

more options

hi, those builds are not ready yet, so you can still overwrite the addon signing requirement with that preference in firefox 47.

more options

Hello philipp,

Thanks for the prompt reply. I appreciate that.

Are you sure "xpinstall.signatures.required" is still relevant in 47? I've read somewhere it isn't.

BR

more options

Valgt løsning

yes i'm fairly sure about this. there was a chanage of plans about this recently - addon signing will only be enforced once those unbranded builds are fully available & that's targeted for firefox 48 for now. https://wiki.mozilla.org/Addons/Extension_Signing#Timeline

more options

Hello philipp,

Thanks again for the important info.

Best regards.

more options

The Unbranded page had been being updated, and was changed to 49.0.1 promptly, when it was public.

FF 49.0.2 has been public for several days, and the unbranded page has not been updated to 49.0.2 yet. Is the Unbranded version that allows my unsigned plugin, going to continue being supported? Help!

more options

Wad I supposed to check the Needs more info box? Just did.

The Unbranded page had been being updated, and was changed to 49.0.1 promptly, when it was public.

FF 49.0.2 has been public for several days, and the unbranded page has not been updated to 49.0.2 yet. Is the Unbranded version that allows my unsigned plugin, going to continue being supported? Help!