Closed
Bug 65142
Opened 25 years ago
Closed 25 years ago
SSL3 clients gets EOF from TLS-only server
Categories
(NSS :: Libraries, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
3.2
People
(Reporter: nelson, Assigned: nelson)
Details
Attachments
(1 file)
|
1.99 KB,
patch
|
Details | Diff | Splinter Review |
Julien Pierre reports that when an NSS-based SSL3 client without
TLS attempts to contact an NSS-based TLS server without SSL3,
the client gets error -5938 PR_END_OF_FILE_ERROR from PR_Send.
The server reports SSL_ERROR_NO_CYPHER_OVERLAP.
Julien would rather that the client experience something like
SSL_ERROR_NO_CYPHER_OVERLAP.
| Assignee | ||
Comment 1•25 years ago
|
||
This is easy to fix, I think.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → 3.2
| Assignee | ||
Comment 2•25 years ago
|
||
Comment 3•25 years ago
|
||
OK, these look good as well.
bob
Comment 4•25 years ago
|
||
Just want to make sure : will these changes address the EOF both for SSL3 client
connecting to TLS-only server; and TLS client connecting to SSL3-only server
(in which case the server gets EOF) ?
Thanks.
| Assignee | ||
Comment 5•25 years ago
|
||
Julien, these patches change some behavior of both NSS SSL clients
and NSS SSL servers. Whether the server reports EOF or another
error depends on client behavior.
I would like you to test these changes for me, to ensure they
accomplish what you expect them to. I can make a build of these
libs available for you. Pls call to arrange.
| Assignee | ||
Comment 6•25 years ago
|
||
I have checked in the patch shown above.
Julien, I'd like you to arrange to test this and let me know
if it's sufficient before I close this bug.
Comment 7•25 years ago
|
||
Nelson,
If you have the patch on a 3.1 build then I can easily rerun my test. But if
it's on a 3.2 then it might take a while until I get the server to work with it.
| Assignee | ||
Comment 8•25 years ago
|
||
It's only on NSS 3.2.
| Assignee | ||
Comment 9•25 years ago
|
||
I'm marking this fixed. If Julien later discovers that it's not
to his satisfaction, this bug can be reopened.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 10•25 years ago
|
||
I verified this as fixed FYI.
You need to log in
before you can comment on or make changes to this bug.
Description
•