Closed
Bug 227991
Opened 22 years ago
Closed 22 years ago
nsNSSCertificateDB::AddCertFromBase64 crashes
Categories
(NSS :: Libraries, defect)
NSS
Libraries
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Bienvenu, Assigned: Bienvenu)
Details
Attachments
(1 file)
632 bytes,
patch
|
KaiE
:
review+
mscott
:
superreview+
|
Details | Diff | Splinter Review |
nsNSSCertificateDB::AddCertFromBase64 crashes because of a call to
CERT_DestroyCertificate that destroys a cert that's been cleaned up with
CERTCertificateCleaner. Patch upcoming
![]() |
Assignee | |
Comment 1•22 years ago
|
||
My bad - I didn't test my new patch correctly after I was advised to add this
call to CERT_DestroyCertificate :-( I didn't clean out my cert db, I guess, so I
didn't hit this code again.
this is fallout from bug 221329 - the bug won't affect any existing
clients/users because this is a new interface but I do need to fix this the new
user of this interface.
![]() |
Assignee | |
Comment 2•22 years ago
|
||
just remove the call to CERT_DestroyCertificate
![]() |
Assignee | |
Updated•22 years ago
|
Attachment #137163 -
Flags: superreview?(mscott)
Attachment #137163 -
Flags: review?(kaie)
Comment 3•22 years ago
|
||
Comment on attachment 137163 [details] [diff] [review]
proposed fix
r=kaie
thanks!
Attachment #137163 -
Flags: review?(kaie) → review+
![]() |
Assignee | |
Comment 4•22 years ago
|
||
Kaie, can you check this in for me once Scott gives his sr? I don't think I can
check into the security directory (can't remember if that was a problem before
or not).
Comment 5•22 years ago
|
||
David, to my knowledge the additional restrictions on security/manager/ have
been dropped over a year ago - your account should be fine to check it in.
But if you experience problems or prefer me to do it, I'm glad to help.
![]() |
||
Updated•22 years ago
|
Attachment #137163 -
Flags: superreview?(mscott) → superreview+
![]() |
Assignee | |
Comment 6•22 years ago
|
||
fix checked in, a=sspitzer over aim.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•