Closed Bug 70926 Opened 24 years ago Closed 23 years ago

unable to open any site with ssl

Categories

(Core Graveyard :: Security: UI, defect)

1.0 Branch
x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ju.nielsen, Assigned: javi)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-5.0 i686; en-US; 0.8) Gecko/20010216
BuildID:    2001021614



Reproducible: Always
Steps to Reproduce:
Download mozilla-0.8.2.i386mrpm and mozilla-psm.0.8.2.i386.rpm
and install both. Then use any site with ssl. 
Absolutely nothing happens. No error-description.


Actual Results:  Nothing

Redhat 6.2 with standard updates.
RPM-files install without anny errors
Executing the "start-psm" program does not make any difference
Various rpm-tools seem to indicate that the mozilla/psm files are installes
wihtout any errors. No libraries are missing.
*** Bug 70927 has been marked as a duplicate of this bug. ***
*** Bug 70927 has been marked as a duplicate of this bug. ***
->crypto
Assignee: mstoltz → javi
Component: Security: General → Security: Crypto
Summary: unable to open any wite with ssl → unable to open any site with ssl
Changed summary from:
unable to open any wite with ssl

to:
unable to open any site with ssl
Works fine for me with 030505 builds on linux, win32 and mac.  I was able to
connect to https://www.sourceforge.net withhout any problems.  Additionally I
was able to log into sourceforge via ssl login.
I found the solution: I must disable TLS before using a site with SSL.
I have not found anything on this issue in the documentation. 
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.