Project

General

Profile

Actions

Bug #3401

open

Firefox extension is unsigned

Added by Junxiao Shi almost 9 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Start date:
01/07/2016
Due date:
% Done:

0%

Estimated time:

Description

Steps to reproduce:

  1. download ndn-protocol.xpi from GitHub repository
  2. drag the downloaded file into Firefox 43.0 for Linux Mint

Expected: add-on is installed

Actual: "This add-on could not be installed because it has not been verified"

Solution: sign the add-on

Actions #1

Updated by Junxiao Shi almost 9 years ago

This issue is urgent because it effectively prevents anyone from installing the add-on.

NFD call recording distribution currently depends on this add-on.

Actions #2

Updated by Anonymous almost 9 years ago

  • Assignee set to Anonymous

The add-on is now signed. I did not list on the Mozilla add-ons site so that the signing process is automatic. Of course, needing to sign makes it more difficult for developers to experiment with updates to the add-on. A developer could sign the add-on separately, but I think they would need to change the name of the add-on. Some choices:

  1. Explain to developers how to use about:config to temporarily disable the signing requirement for all add-ons.
  2. Provide an easy way to change the name of the add-on so that a developer can submit it to be signed.

What do you think?

Actions #3

Updated by Anonymous almost 9 years ago

  • Status changed from New to Resolved
Actions #4

Updated by Junxiao Shi almost 9 years ago

The add-on GUID, along with other parameters for invoking signing API, should be accepted on the ./configure line or in environ.

A link to documentation on how to disable signing requirement should be included, so that a developer can debug the add-on.
This is only for debugging, not for redistribution.

Actions #5

Updated by Anonymous almost 9 years ago

  • Project changed from 3 to NDN in the browser
Actions #6

Updated by Anonymous almost 9 years ago

Hi Junxiao. I found this FAQ from Mozilla. The recommendation for developing and experimenting with add-ons is to use the "unbranded" build which is the same as the release build but has an about:config setting to allow unsigned add-ons. (It's unpractical to submit a new version to be signed with every change during development.) I'll update the instructions to use the unbranded build.
https://wiki.mozilla.org/Add-ons/Extension_Signing#FAQ

Actions #7

Updated by Anonymous almost 9 years ago

Mozilla now says that the unbranded version will be available for Firefox 46, scheduled for April 19.
https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/

In the mean time the recommended solution for testing is to use about:config to set xpinstall.signatures.required to false. We'll keep this issue open until the unbranded version is available.

Actions #8

Updated by Anonymous over 8 years ago

  • Priority changed from Urgent to Normal

The Firefox 46 release is delayed until April 26.

Actions #9

Updated by Anonymous over 8 years ago

My Firefox updated to version 46, and setting xpinstall.signatures.required to false still works. Maybe now we wait for Firefox 47 on June 7?

Actions #10

Updated by Anonymous over 1 year ago

  • Assignee deleted (Anonymous)
Actions

Also available in: Atom PDF