Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Unbranded Builds

  • 6 réponses
  • 3 ont ce problème
  • 54 vues
  • Dernière réponse par 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.

Modifié le par Yaron

Solution choisie

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

Lire cette réponse dans son contexte 👍 1

Toutes les réponses (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

Solution choisie

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!