question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Distribute Signed Extension for Firefox

See original GitHub issue

The current extension is not signed and firefox complains about it.

so I went ahead and signed it for myself.

here is the process to sign first clone the repo git clone https://github.com/jasonlong/isometric-contributions.git then do npm install --global web-ext what is web-ext? Web-ext docs Web ext getting started

now go ahead and generate JWT issuer and JWT secret from add-on developer hub. it is like API key for signing the extension.

now cd into <extension-repo>/firefox/isometric-contributions/ then run this command to sign web-ext sign --api-key <your-JWT-issuer> --api-secret <your-JWT-secret>

this should give you a signed extension(.xpi file) inside a folder named web-ext-artifacts inside your current working directory

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:1
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
jasonlongcommented, Feb 15, 2017

Ok, finally got the problem worked out and got the add-on submitted for review.

2reactions
jasonlongcommented, Feb 10, 2017

Thanks for this info @electron0zero. I’m not very familiar with Firefox’s extensions and didn’t realize the progress they’d made since last I looked.

I’ve gone ahead and started the process of uploading the extension to addons.mozilla.org (ran into an error that I emailed them about) and, if I understand right, they will sign the .xpi on their end. If so, I assume I don’t need to bother with the steps you listed here. Is that correct?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Signing and distributing your add-on - Extension Workshop
This signing process takes place through addons.mozilla.org (AMO), whether you choose to distribute your add-on through AMO or to do it ...
Read more >
Add-ons/Extension Signing - MozillaWiki
Mozilla requires all extensions to be signed by Mozilla in order for them to be installable in Release and Beta versions of Firefox....
Read more >
Add-on signing in Firefox - Mozilla Support
Mozilla verifies and "signs" add-ons that follow a set of security guidelines. All add-ons hosted on addons.mozilla.org have to go through this process...
Read more >
Introducing Extension Signing: A Safer Add-on Experience
An easy solution would be to force all developers to distribute their extensions through AMO, like what Google does for Chrome extensions.
Read more >
Deploying Firefox with extensions - Mozilla Support
In an enterprise environment, it may be necessary to deploy Firefox with a set of predefined extensions. This can be done easily on...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found