Closed
Bug 67392
Opened 24 years ago
Closed 22 years ago
CERT_ImportCAChain does not persist certs if they already exist in the temporary database
Categories
(NSS :: Libraries, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
3.4
People
(Reporter: julien.pierre, Assigned: rrelyea)
Details
Attachments
(1 file)
2.13 KB,
patch
|
Details | Diff | Splinter Review |
The title is self explicit. See certhigh.c , line 792.
Comment 1•24 years ago
|
||
Julien's right. This code seems wrong. This code checks to see if the cert is already in the TEMP cert db and if so, simply refuses to try to save it in the PERM cert db. Perhaps it was the author's intent to check to see if it was already in the PERM cert db, and the error was that it's checking the wrong db. Or, perhaps it was the author's intent to see if it's in the temp DB, and if so, skip the steps of importing it into the temp DB and go straight to the step of saving the temp cert in the perm cert db, and the error is that it is skipping it alltogether instead of saving in the perm cert db. Either way, if the cert is already in the temp cert db, this function won't save it in the perm. And that just seems wrong. The workaround is to delete the cert from the temp cert db before calling this function.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows NT → All
Comment 2•24 years ago
|
||
Julien, can you use the workaround that Nelson suggested? Bob, I'm assigning this bug to you for your triage.
Assignee: wtc → relyea
Reporter | ||
Comment 3•24 years ago
|
||
Wan-Teh, I'm already using the workaround. But I'd still like to see the bug fixed in the future.
Assignee | ||
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
Bob, I think you attached the patch to the wrong bug :)
Assignee | ||
Comment 6•24 years ago
|
||
I sure did ooops....
Updated•24 years ago
|
Priority: -- → P3
Target Milestone: --- → 3.3
Comment 7•23 years ago
|
||
Bob, is this fixed or should we move the target to 3.4?
Assignee | ||
Comment 8•23 years ago
|
||
Move it to 3.4 bob
Updated•23 years ago
|
Target Milestone: 3.3 → 3.4
Comment 9•22 years ago
|
||
Changed the QA contact to Bishakha.
QA Contact: sonja.mirtitsch → bishakhabanerjee
Assignee | ||
Comment 11•22 years ago
|
||
OK, I've finally had a chance to look at this with respect to 3.4, and 3.4 no longer checks for the cert in the temp DB before importing it.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 12•22 years ago
|
||
Changed target milestone to 3.4 per Bob's comment #11.
Target Milestone: 3.5 → 3.4
You need to log in
before you can comment on or make changes to this bug.
Description
•