Closed Bug 72405 Opened 25 years ago Closed 24 years ago

Mozilla PSM won't accept new certificates

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch
x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED
psm2.0

People

(Reporter: dylang, Assigned: ddrinan0264)

References

()

Details

Webmail on thock.com is secured via SSL. Since the SSL is used only for encryption (and not encryption and trust-metric stuff), it's a self-signed certificate. Mozilla pops up a nice "this is a new cerificate" dialog when I head to the site, but I am never able to get past the second step without a hang within the dialogs. SSL is effectively broken for what I need it for in Mozilla build 2001031611
Dylan, the hostname web.thock.com does not resolve. Could you please check that URL?
Confirming. A workaround is to accept the certificate in Nav 4.7 on Linux or windows, then overwrite the cert7.db and key3.db files in the .mozilla directory with the ones from your .netscape directory or windows profile directory. This probably won't get fixed for PSM 1.5 since we are working on PSM 2.0.
Status: UNCONFIRMED → NEW
Ever confirmed: true
It resolves. The DNS servers run on djbdns, which might not be interacting well with your copy of bind. Just try a second time.
I can reproduce this in 0.8.1, but only when Javascript is not enabled. It would be nice if accepting new certificates would work witouht enabling Javascript, though.
The javascript issue is bug 65378
*** Bug 72672 has been marked as a duplicate of this bug. ***
Marking fixed now that PSM 2.0 is included in the nightly mozilla builds.
Status: NEW → RESOLVED
Closed: 24 years ago
Priority: -- → P3
Resolution: --- → FIXED
Target Milestone: --- → 2.0
Version: unspecified → 2.0
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.