Closed
Bug 1195671
Opened 9 years ago
Closed 7 years ago
Installing a self-signed add-on results in a "corrupted" warning instead of a "blocked uncertified add-on" warning
Categories
(Toolkit :: Add-ons Manager, defect, P4)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
DUPLICATE
of bug 1213728
People
(Reporter: designakt, Unassigned)
References
()
Details
(Whiteboard: [error])
Attachments
(1 file)
|
114.62 KB,
image/png
|
Details |
Unsigned-Add-on-corrupt-Warning.png
Trying to install a dev-build of adblock plus results in a corrupted warning.
https://adblockplus.org/en/development-builds#installation
|
Reporter | |
Updated•9 years ago
|
Blocks: signed-addons
|
||
Comment 1•9 years ago
|
||
The problem is that those adblock builds are signed, just not with a Mozilla certificate. Adblock have been signing their builds with their own certificate for a while. I'm not sure if we have an easy way to detect the difference between the two right now.
Summary: Installing an unsigned add-on results in a "corrupted" warning instead of a "blocked uncertified add-on" warning → Installing a self-signed add-on results in a "corrupted" warning instead of a "blocked uncertified add-on" warning
|
|
Reporter | |
Comment 2•9 years ago
|
||
Does their signing make it a verified add-on? Or do they still count as unverified?
|
|
||
Comment 3•9 years ago
|
||
(In reply to Markus Jaritz [:maritz] (UX) from comment #2)
> Does their signing make it a verified add-on? Or do they still count as
> unverified?
It should still be unverified.
|
|
||
Updated•9 years ago
|
|
||
Updated•9 years ago
|
|
||
Updated•9 years ago
|
Severity: normal → minor
Priority: -- → P4
Whiteboard: [error]
|
||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•