Skip to content
This repository has been archived by the owner. It is now read-only.

[New Devtools] Firefox requires a signed addon #136

Closed
julen opened this issue Aug 10, 2015 · 13 comments
Closed

[New Devtools] Firefox requires a signed addon #136

julen opened this issue Aug 10, 2015 · 13 comments

Comments

@julen
Copy link

@julen julen commented Aug 10, 2015

Starting from Firefox 41 (currently on the Aurora channel), add-on signing is enforced (42 onwards it will be mandatory), so unsigned addons are disabled by Firefox, leaving no way to run the new devtools 馃槥

Not sure if 3rd parties can sign addons themselves; other than that signing will be done for any addons that are available on AMO and have gone through their review process.

@jaredly
Copy link
Contributor

@jaredly jaredly commented Aug 10, 2015

We're planning on going through AMO for the official release
On Mon, Aug 10, 2015 at 5:27 AM Julen Ruiz Aizpuru notifications@github.com
wrote:

Starting from Firefox 41 (currently on the Aurora channel), add-on signing
is enforced (42 onwards it will be mandatory
http://www.ghacks.net/2015/06/19/how-to-disable-the-firefox-40-add-on-signing-requirement/),
so unsigned addons are disabled by Firefox, leaving no way to run the new
devtools [image: 馃槥]

Not sure if 3rd parties can sign addons themselves; other than that
signing will be done for any addons that are available on AMO and have gone
through their review process.


Reply to this email directly or view it on GitHub
#136.

Loading

@fjaguero
Copy link

@fjaguero fjaguero commented Aug 17, 2015

As commented by @julen, Firefox Developer Edition no longer allows un-signed add-ons, so it's not possible to use it now.

Loading

@ngyikp
Copy link
Contributor

@ngyikp ngyikp commented Aug 17, 2015

It's still possible to load unsigned extensions on non-release/beta Firefox by changing xpinstall.signatures.required at about:config.

Loading

@mtrenker
Copy link

@mtrenker mtrenker commented Aug 17, 2015

The versions were fixed in the wiki, react tools will continue to work with FX up to and including 42 (Developer Edition) with the config change @ngyikp mentioned.

Loading

@breathe
Copy link

@breathe breathe commented Sep 4, 2015

Sorry to chime in on this issue with what may be a user issue -- but is there a signed addon somewhere now -- that is to say -- is there supposed to be a signed version of the 0.14 release for firefox published somewhere?

This is the only url I can find and it seems to offer 0.14.1 without signature? https://addons.mozilla.org/en-US/firefox/addon/react-devtools/

Loading

@fjaguero
Copy link

@fjaguero fjaguero commented Sep 4, 2015

@breathe There is no signed version. You should do what @ngyikp said to allow the newest Firefox version to enable the extension.

Loading

@sophiebits
Copy link
Contributor

@sophiebits sophiebits commented Sep 4, 2015

AFAIK we just need to wait for Mozilla to review it.

Loading

@mezod
Copy link

@mezod mezod commented Sep 24, 2015

20 days later...still unsigned

Loading

@sophiebits
Copy link
Contributor

@sophiebits sophiebits commented Sep 24, 2015

I don't know of any way to speed up the process. Sorry.

Loading

@mezod
Copy link

@mezod mezod commented Sep 24, 2015

I'm asking at #amo-editors @ irc.mozilla.org to see if this can be sorted out asap

Loading

@digitarald
Copy link
Contributor

@digitarald digitarald commented Sep 25, 2015

The switch to signing definitely took a toll on the backlog but the interface should give an indication. I pinged the review team on this.

Loading

@sophiebits
Copy link
Contributor

@sophiebits sophiebits commented Sep 25, 2015

It was 100 of 150 in the queue when I checked earlier today. So probably a month or two at that rate.

Loading

@sophiebits
Copy link
Contributor

@sophiebits sophiebits commented Oct 3, 2015

The addon has now passed preliminary review.

Loading

@sophiebits sophiebits closed this Oct 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants