Patches for add-on signing intermediate certificate dot release do not work if security.nocertdb is set to true

RESOLVED DUPLICATE of bug 1549249

Status

()

defect
RESOLVED DUPLICATE of bug 1549249
Last month
Last month

People

(Reporter: gk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [cert2019])

Reporter

Description

Last month

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

Last month
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
Status: NEW → RESOLVED
Closed: Last month
Resolution: --- → DUPLICATE
Duplicate of bug: 1549249
You need to log in before you can comment on or make changes to this bug.