TLS fail to work in Firefox

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
9 years ago
6 years ago

People

(Reporter: ilies.radu, Unassigned)

Tracking

1.9.2 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTB6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTB6

Tested with:
* Firefox 3.5.7 [windows / mac / linux]
* Firefox 3.6 [windows / mac]

Reproducible: Always

Steps to Reproduce:
1. Disable in Firefox SSLV3 and keep enabled TLSv1 and RESTART BROWSER
2. Type in browser: https://86.122.12.131/
3. Accept the unsigned certificate

Actual Results:  
Connection Reset

Expected Results:  
The Page should be visible.
All other browsers work perfectly (tested with):
* Safari
* Internet Explorer
* Opera
* Konqueror

This bug is not generaly available.
It is reproduced only with certain version of server's OpenSSL.
In this case i found that the OpenSSL Version on server is: OpenSSL 0.9.9-dev 09 May 2008, on NetBSD 5.0.1 (64-bit).
Maybe there are also certain other versions of OpenSSL that will lead firefox with the same bug (who knows ...?).
My concern is that all the rest of the browsers have NOT FAILED on this but only Firefox.
Assignee: nobody → kaie
Severity: critical → normal
Component: General → Security: PSM
Product: Firefox → Core
QA Contact: general → psm
Version: unspecified → 1.9.2 Branch

Comment 1

9 years ago
Mass change owner of unconfirmed "Core:Security UI/PSM/SMime" bugs to nobody.
Search for kaie-20100607-unconfirmed-nobody
Assignee: kaie → nobody

Comment 2

8 years ago
This seems to work properly in FF 5 beta
Reporter; Is this still an issue ?
Whiteboard: [CLOSEME 2012-12-30]

Comment 4

6 years ago
Resolved per whiteboard and Comment 2
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Whiteboard: [CLOSEME 2012-12-30]
You need to log in before you can comment on or make changes to this bug.