Closed Bug 508291 Opened 12 years ago Closed 12 years ago

TLS -only- secure connections, stop working if stop is clicked while data are transferred

Categories

(Core :: Security: PSM, defect)

x86
All
defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: asemere, Assigned: KaiE)

References

Details

(Whiteboard: [probably dup of bug 498311])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2

any attempt to establish a new secure connection, returns a message that SSL is disabled.

SSLv2 and SSLv3 are disabled. only TLS is enabled and used, with these cryptography algorithms: security.ssl3.ecdh_ecdsa_aes_256_sha, security.ssl3.ecdhe_ecdsa_aes_256_sha and security.ssl3.rsa_aes_256_sha.

this happens with every server that firefox had an established secure connection that was interrupted by clicking stop.

this prevents further connections to each server with TLS connections that were interrupted. not globally.

it works again only if the current firefox instance is exited and a new instance is started.

Reproducible: Always
Component: General → Security
Version: unspecified → 3.5 Branch
Assignee: nobody → kaie
Component: Security → Security: PSM
Product: Firefox → Core
QA Contact: general → psm
Version: 3.5 Branch → Trunk
Setting to confirmed. I believe this.

I guess some error codes for interrupted connections cause us to treat the site as TLS intolerant and stop using TLS for the site.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Isn't this a dup of bug 498311?
Question for the reporter.
> SSLv2 and SSLv3 are disabled.
Do you mean on the server?  Or do you mean in your browser?

If you have disabled them in your browser, then this bug seems more like 
a dup of bug 368130, which is allegedly fixed.
Depends on: 498311
Whiteboard: [probably dup of bug 498311]
today i downloaded and began using Firefox 3.6. it works properly now. :)

mayhemer, i think not.

MisterSSL, in the browser of course!

thank you
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.