Closed
Bug 88244
Opened 23 years ago
Closed 23 years ago
Need a way to re-try SSL connections w/ TLS turned off
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.1
People
(Reporter: javi, Assigned: javi)
References
Details
Attachments
(1 file)
12.48 KB,
patch
|
Details | Diff | Splinter Review |
This bug is a result of Bug 87902
Basically, the current necko/PSM architecture makes it very hard to re-try a
connection the failed because the server on the other end does not implement TLS
(aka SSL v3.1) correctly.
In the PSM layer, we won't know if we're talking to a TLS intolerant site until
the first write. At this point the server will have shut down the connection so
we'd like to set an error (ie NS_ERROR_TLS_INTOLERANT_SERVER) and have necko
re-try the connection only it tells us to turn off TLS before establishing the
connection a second time.
That will make it easier to support TLS intolerant servers when talking through
a proxy and will allow us to get rid of the current work around in the PSM layer.
The other option is to use evangelism rather than code to fix the problem.
We're exploring this option.
Comment 2•23 years ago
|
||
we already have code which automatically restarts an HTTP transaction if the
first socket read returns EOF (0 bytes read with PR_SUCCESS), which can happen
even after writing out data to the socket. so, it might be possible for PSM to
simply force a premature EOF, which would make HTTP retry with a new socket.
so, all we'd need to figure out is how to tell PSM to not use TLS. suggestions?
is there any way that PSM can keep a list of TLS intolerant servers?
Assignee | ||
Comment 3•23 years ago
|
||
We'd have to add a method to the nsISSLSocketControl interface disableTLS that
would get called on the second socket that is created. Also we could do a
PR_SetError with a new error code so you'd know this was a TLS intolerant server.
Seems like that should be enough.
Comment 4•23 years ago
|
||
moving milestone. Javi, if you have a patch, we can try to get this into 0.9.2.
Target Milestone: --- → mozilla1.0
Comment 5•23 years ago
|
||
err.0.9.3
Assignee | ||
Comment 6•23 years ago
|
||
->PSM
Component: Networking → Client Library
Product: Browser → PSM
Target Milestone: mozilla1.0 → 2.1
Version: other → 2.1
Comment 10•23 years ago
|
||
*** Bug 88142 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 11•23 years ago
|
||
Comment 12•23 years ago
|
||
It looks fine to me, from the necko side of things. darin?
Comment 13•23 years ago
|
||
r=ddrinan.
Assignee | ||
Updated•23 years ago
|
QA Contact: benc → junruh
Comment 14•23 years ago
|
||
the communication to necko looks good to me.
Comment 15•23 years ago
|
||
sr=blizzard
Assignee | ||
Comment 16•23 years ago
|
||
patch checked in.
TLS is no longer turned off for all proxied SSL connections.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
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
•