Closed
Bug 76975
Opened 24 years ago
Closed 22 years ago
[MLK] Leaking C strings in nsNSSComponent::ConfigureInternalPKCS11Token()
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
VERIFIED
WONTFIX
Future
People
(Reporter: beard, Assigned: javi)
References
()
Details
(Keywords: memory-leak)
All the calls to GetPK11String() in this method allocate strings. The call to
PK11_ConfigurePKCS11() at the bottom of the method evidently copies all of those
strings, thus all of the allocated strings leak. The URL above points to just one
of the lines where a leaked string is allocated.
Assignee | ||
Updated•24 years ago
|
Component: Libraries → Client Library
Product: NSS → PSM
Target Milestone: --- → 2.0
Version: 3.0 → 2.0
Assignee | ||
Comment 1•24 years ago
|
||
This is a one time leak caused by NSS not freeing the strings passed in for
intializing the token names. A possible work around is to declare our own
global static char arrays and populate and pass it to the PK11 libraries.
This is a one time less than 300 bytes.
Updated•23 years ago
|
Keywords: nsenterprise
Comment 5•23 years ago
|
||
Moving all P3 and P4 bugs targetted to 2.1 to future.
Target Milestone: 2.1 → Future
Comment 6•23 years ago
|
||
Changed the QA contact to Bishakha.
QA Contact: sonja.mirtitsch → bishakhabanerjee
Comment 7•22 years ago
|
||
This is not a PSM bug.
PSM by itself is not leaking (at least it does no longer leak, if it ever leaked
in the past).
PSM passes internal buffers of automatic strings to PK11_ConfigurePKCS11. It
will free the temporaray strings after the call.
If you think NSS is leaking and should free its strings on shutdown, please
reopen and change this into a NSS bug.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Comment 8•22 years ago
|
||
I think this was fixed in another bug (perhaps even one filed after this one).
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•