Closed
Bug 1549344
Opened 6 years ago
Closed 6 years ago
Patches for add-on signing intermediate certificate dot release do not work if security.nocertdb is set to true
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
DUPLICATE
of bug 1549249
People
(Reporter: gk, Unassigned)
References
Details
(Whiteboard: [cert2019])
Back in bug 629558 an option got introduced to make the intermediate certificate store memory-only. But setting the security.nocertdb
preference to true
does not get the patches for armagadd-on 2.0 applied.
Now to keep the properties we get from setting security.nocertdb
, we moved forward to just disable the pref, add the new cert, and re-enable it, which kind of worked but it seems after a restart and sufficient amount of time passing so that a re-check is triggered the extensions get disabled again.
Thus, we redo a -build2 for Tor Browser with the pref disabled.
However, it would be nice to get the security.nocertdb
preference working again as intended.
Reporter | ||
Updated•6 years ago
|
Summary: Patches add-on signing intermediate certificate dot release do not work if security.nocertdb is set to true → Patches for add-on signing intermediate certificate dot release do not work if security.nocertdb is set to true
Whiteboard: [cert2019]
Component: General → Add-ons Manager
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•