Closed
Bug 140936
Opened 23 years ago
Closed 23 years ago
OSCP fails with error code -8073
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 130885
People
(Reporter: Piotr.Sulecki, Assigned: ssaux)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; pl-PL; rv:1.0rc1) Gecko/20020417
BuildID: 2002041711 (1.0 RC1 Polish)
When loading this page SSL should be turned on. However, the verification of
site's certificate fails with the error code -8073 (anybody knows what this
means?) As a result, the page is not loaded.
If I disable the OSCP verification (Preferences/Security/Verification or
something like that, I'm using the Polish interface), I am able to log in but
[Mozilla says that] the encryption is disabled.
The same page viewed with Netscape 4.77 works correctly. It worked correctly
with versions 0.9.6 - 0.9.9, and I'm not 100% sure but only 80% or so but I
think it did work even with 1.0RC1 before. I suspect it has something to do with
the fact that the site's certificate has expired on April 24 or so; however, the
site's certificate is updated and NS 4.77 shows correct certificate information.
I don't see the site's certificate in Certificate Manager. I deleted the
cert7.db file to force re-creation of it and it didn't help, so I don't think
it's a certificate problem.
Reproducible: Always
Steps to Reproduce:
1. I just load the given URL,
2. ... and I get a window saying the certificate validity could not be verified,
and the above error code.
Comment 1•23 years ago
|
||
-> PSM
see also bug 110842 or bug 126187
Comment 2•23 years ago
|
||
-> PSM (second try)
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: bsharma → junruh
Version: other → unspecified
Comment 3•23 years ago
|
||
*** This bug has been marked as a duplicate of 130885 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•