118669 - Unable to log into secure sites

Status: VERIFIED WORKSFORME

(Core Graveyard :: Security: UI, defect)

Description

[Jim Berwick]

Using a fresh trunk pull from today, building with BUILD_PSM2=1, I am unable to
log into any secure sites.  Summary is a bit vague, but I can't think of a
better way to describe it.

Steps to reproduce:
Go to mail.yahoo.com
Click the "Secure" link.
Mozilla will wait for a long time (5 to 10 seconds) and then say "Connection was
refused when contacting login.yahoo.com"
The browser now freezes completely for a few moments (5 or 10 seconds).
At this point, the title bar blinks non stop.  Windows 2000 task bar shows it
highlighted in blue if not the active screen.  This does not stop until I close
the browser.  

I have check mozilla.org/security and the correct .dll files have been built and
are in the proper locations, and I recieved no build errors nor does it appear
that PSM is not installed, only I can not do anything with https: sites.

Actual Results:
Mozilla does not connect to any secure sites, hangs for a little bit and causes
an annoying blinking on my taskbar :)

Expected Results:
I should be able to view a secure site, or Mozilla should pop up an error of
some type telling me either PSM isn't installed, is installed but something
isn't working right, or at this point, just crash, cause anything is better than
the title bar and taskbar blinking at me non stop while I'm trying to fill out a
bug report.  I can provide more info, copies of the appropriate .dll's, anything
from *.js, whatever is necessary.  I can't stand having to use IE for my
"secure" transactions, it is almost an oxymoron having IE and secure in the same
sentence

Comment 1

[Stephane Saux]

Daily builds from release engineering do not have this problem. 
There may be something wrong in the way you've built your tree.
There may be something wrong with your cert database. Try a new profile.

Works for me.

Comment 2

[John Unruh]

Verified WFM.

Comment 3

[Jim Berwick]

The cause of the problem was rogue entries in prefs.js.  Unsure of how they got there, or which in particular caused the problem, but the problem was there and not related to the cert databases