If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Calling SSL_SetSockPeerID a second time leaks the previous value

RESOLVED FIXED in 3.12.4

Status

NSS
Libraries
P2
normal
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: Nelson Bolyard (seldom reads bugmail), Assigned: Nelson Bolyard (seldom reads bugmail))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Also, there doesn't appear to be any way to unset the previously set 
value.  These things can all be fixed by small low-risk changes to 
SSL_SetSockPeerID.
(Assignee)

Updated

9 years ago
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → 3.12.4
Created attachment 371201 [details] [diff] [review]
Proposed patch v1 for CVS trunk (untested)

I think this will do the trick.
Attachment #371201 - Flags: review?(rrelyea)

Updated

9 years ago
Attachment #371201 - Flags: review?(rrelyea) → review+

Comment 2

9 years ago
Comment on attachment 371201 [details] [diff] [review]
Proposed patch v1 for CVS trunk (untested)

r+
Thanks Bob.

Checking in ssl/sslsock.c; new revision: 1.57; previous revision: 1.56
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.