Closed
Bug 372787
Opened 19 years ago
Closed 12 years ago
erroneous block comment for ssl3_DestroySSL3Info
Categories
(NSS :: Libraries, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
3.11.7
People
(Reporter: lintan2, Assigned: nelson)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier:
/* Called from ssl_FreeSocket() in sslsock.c */
void
ssl3_DestroySSL3Info(sslSocket *ss)
According to the block cooment, shouldn't ssl3_DestroySSL3Info() be called from
ssl_FreeSocket()?
I found it iss called from ssl_FreeSocket() from two path, but not the following one.
call chain: SSL_ImportFD -> ssl_NewSocket -> ssl_DestroySocketContents
The two call chains that follow the comment are:
SSL_ImportFD -> ssl_FreeSocket -> ssl_DestroySocketContents
ssl_Accept -> ssl_FreeSocket -> ssl_DestroySocketContents
Reproducible: Always
| Assignee | ||
Comment 1•19 years ago
|
||
ssl_DestroySocketContents unconditionally calls ssl3_DestroySSL3Info.
The block comment should be updated to say that.
ssl_FreeSocket unconditionally calls ssl_DestroySocketContents.
ssl_NewSocket only calls ssl_DestroySocketContents upon failure.
I think I should combine this bug with bug 369802.
We shuold not do a checkin specifically to correct this comment, but the
next time we need to modify that file, we should correct this comment.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4
Summary: ssl3_DestroySSL3Info() is NOT called from ssl_FreeSocket() → erroneous block comment for ssl3_DestroySSL3Info
Version: unspecified → 3.4
Comment 2•12 years ago
|
||
This was done as part of Bug 373276:
https://hg.mozilla.org/projects/nss/diff/8c957268885e/security/nss/lib/ssl/ssl3con.c#l1.400
(Or if preferred: http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/security/nss/lib/ssl&command=DIFF&root=/cvsroot&file=ssl3con.c&rev1=1.100&rev2=1.101#15 )
Assignee: nobody → nelson
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.11.7
You need to log in
before you can comment on or make changes to this bug.
Description
•