make CertVerifier directly aware of 3rd party roots rather than going through NSS
Categories
(Core :: Security: PSM, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox64 | --- | wontfix |
firefox65 | --- | wontfix |
firefox66 | --- | wontfix |
firefox67 | --- | fixed |
People
(Reporter: ronoc74, Assigned: keeler)
References
(Blocks 1 open bug)
Details
(Keywords: regression, Whiteboard: [psm-assigned])
Attachments
(3 files)
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Comment 4•6 years ago
|
||
Assignee | ||
Comment 5•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 7•6 years ago
|
||
Assignee | ||
Comment 9•6 years ago
|
||
Reporter | ||
Comment 10•6 years ago
|
||
Reporter | ||
Comment 11•6 years ago
|
||
Assignee | ||
Comment 12•6 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Comment 13•6 years ago
|
||
Assignee | ||
Comment 16•6 years ago
|
||
Before this patch, if the enterprise roots feature were enabled, nsNSSComponent
would gather any such roots and temporarily import them into NSS so that
CertVerifier could use them during path building and trust querying. This turned
out to be problematic in part because doing so would require unlocking the
user's key DB if they had a password. This patch implements a scheme whereby
nsNSSComponent can give these extra roots directly to CertVerifier, thus
bypassing NSS and any need to unlock/modify any DBs. This should also provide a
path forward for other improvements such as not repeatedly searching through all
certificates on all tokens, which has inefficiencies (see e.g. bug 1478148).
Assignee | ||
Comment 17•6 years ago
|
||
Comment 18•6 years ago
|
||
Comment 19•6 years ago
|
||
bugherder |
Comment 20•6 years ago
|
||
Dana, is that something that we would like to uplift in 66 ? thanks
Assignee | ||
Comment 21•6 years ago
|
||
I'd rather not. There's a workaround for this issue and we would have to uplift bug 1520347 as well.
Updated•6 years ago
|
Description
•