Mozilla Add-ons Community Blog
Categories: developers

Add-on Signing Enforcement In Firefox 46 for Android

13 responses

As part of the Extension Signing initiative, signing enforcement will be enabled by default on Firefox 46 for Android. All Firefox for Android extensions on addons.mozilla.org have been signed, and developers who self-host add-ons for Android should ensure those add-ons are signed prior to April 12th, 2016.

Extension signing enforcement can be disabled using the preference outlined in the FAQ, and this preference will be removed in a future release.

More information on Extension Signing is available on the Mozilla Wiki, and information on the change to Firefox for Android can be found on Bugzilla under Bug 1244329.

13 comments on “Add-on Signing Enforcement In Firefox 46 for Android”

  1. Will wrote on

    A deadline almost 2 years in the past? 🙂

    1. Kev Needham wrote on

      I’d like to claim the keys are, like, right next to each other, but… they’re not. Corrected.

  2. John Liebson wrote on

    “…prior to April 12th, 2014” is going to be rather difficult, as today’s date is 17 March 2016.

    1. Kev Needham wrote on

      Agree this would be very difficult, although cool if someone _could_. Corrected.

  3. Anton Maslo wrote on

    I think you meant 2016, not 2014.

    1. Kev Needham wrote on

      I did, indeed. Corrected.

  4. David wrote on

    “should ensure those add-ons are signed prior to April 12th, 2014.”
    2014??? I am pretty sure you mean 2016.

    1. Kev Needham wrote on

      2014 was such a good year, I lost myself in time a little. Thanks for pointing it out, and corrected.

  5. mahendra wrote on

    Can any one make clear that Which add-on types will need to be signed?

  6. John Davis wrote on

    How do I get the HP Client Security Manager add-on/extension signed for use in FF? Currently FF says it is disabled.

    1. Jorge Villalobos wrote on

      Check for updates for the extension, including on HP’s site. It’s up to them to get the add-on signed and distribute the signed version.

  7. pooja wrote on

    Some addon not works properly.

  8. basil wrote on

    I don’t see the unbranded links for firefox yet. So when are those gonna happen, or am I going to stay un-upgraded/switching to other browsers?