Closed
Bug 1213728
Opened 9 years ago
Closed 5 years ago
"addon appears to be corrupt" error when add-on is signed by someone other than Mozilla
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: glob, Unassigned)
References
Details
Attachments
(1 file)
58.64 KB,
image/png
|
Details |
firefox dev-edition 43.0a2 (2015-10-08)
i tried to install the dashline addon from https://d3mfqat9ni8wb5.cloudfront.net/releases/3.5.4/3.5.4.91082/Dashlane.xpi however i receive the following error:
"The add-on downloaded from this site could not be installed because it appears to be corrupt."
this appears to be related to add-on signature checking, as once i changed xpinstall.signatures.required from true to false the error went away.
Comment 2•9 years ago
|
||
This add-on was signed by Digicert not Mozilla so we're doing the right thing by refusing to install it. The error message could possibly be a bit better but I'm not sure how easy that is to improve.
Summary: "addon appears to be corrupt" error with xpinstall.signatures.required set to true → "addon appears to be corrupt" error when add-on is signed by someone other than Mozilla
if you don't want to expose the more technical reason for considering an add-on corrupt to most users (understandable!), would it be possible to log the technical reason to the browser console, or provide some other means to expose the reason why an add-on is considered corrupt?
Comment 4•9 years ago
|
||
Dupe of bug 1224591 (or vice-versa)? See in particular bug 1224591 comment 6 and 7.
Comment 5•9 years ago
|
||
(In reply to Byron Jones ‹:glob› (Unavailable until 4th Jan) from comment #3)
> if you don't want to expose the more technical reason for considering an
> add-on corrupt to most users (understandable!), would it be possible to log
> the technical reason to the browser console, or provide some other means to
> expose the reason why an add-on is considered corrupt?
In this particular case, I see no security risk in changing the message to "Add-on was not signed by Mozilla". Another possibility would be "Signature verification failed" but I suppose it might bring a lot of bug reports DUPLICATE to this one.
Updated•5 years ago
|
Whiteboard: webext?
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Whiteboard: webext?
You need to log in
before you can comment on or make changes to this bug.
Description
•