Closed Bug 178684 Opened 17 years ago Closed 17 years ago
Hidden expired certificate
Cannot connect to https://twist.phys.ualberta.ca after the site certificate has expired and was recreated. Using mozilla-1.2b-20021105, the expired certificate is not listed in edit->preferences->privacy->certificates->web_sites. Using RedHat mozilla-1.0.1-2.7.3, the expired certificate is listed, but cannot be deleted (see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=77411). Attempts to connect to the site yeld an "error code -12193" error dialog rather than the "this site's certificate has expired". Can I manually delete the expired certificate? K.Olchanski
This is another bug opened due to problems with "plesk.com" type server certs, where the issuer and issue are identical, and the serial number is 00. Reporter, you can back up your personal certificates, if any, close the browser, rename the cert7.db file, (which is in a subdidrectory of ~/.mozilla), then restore your personal certs. That is the workaround to reach the above site. "the expired certificate is not listed in edit->prefs->privacy->certs-> web_sites." The cert may be under the Authorities tab - see bug 178692, where you can delete it. "Using RedHat mozilla-1.0.1-2.7.3, the expired certificate is listed, but cannot be deleted" Using a recent nightly build from www.mozilla.org, web site certs can be deleted.
This bug is marked dependent on 175115. But I think it is not. Anyway, you might want to test whether the fix for bug 175115 helped. The patch for bug 175115 just has landed on the 1.2 branch. If you want, get a build from http://bugzilla.mozilla.org/attachment.cgi?id=104600&action=view *tomorrow*. If the problem is fixed on the branch for you, please comment in here. Please do not yet mark the bug as fixed, because we need to wait until the patch for 175115 lands on the trunk, too.
*** This bug has been marked as a duplicate of 182607 ***
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.