We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Unbranded Builds

  • 6 antwurd
  • 3 hawwe dit probleem
  • 5 werjeftes
  • Lêste antwurd fan 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.

Bewurke troch Yaron op

Keazen oplossing

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

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (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

Keazen oplossing

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!