sec_error_expired_issuer_certificate

[Savvas Radevic]

Xubuntu hardy heron 8.04.1 i386
During Live CD, I visited launchpad.net using mozilla firefox, but I got the following errors:

(1)
launchpad.net:443 uses an invalid security certificate.
The certificate is not trusted because the issuer certificate has expired.
The certificate will not be valid until 07/25/2006 06:24 PM.
(Error code: sec_error_expired_issuer_certificate)

(2)
bugs.edge.launchpad.net uses an invalid security certificate.
The certificate is not trusted because the issuer certificate has expired.
The certificate will not be valid until 07/11/2007 10:37 PM.
(Error code: sec_error_expired_issuer_certificate)

3)
edge.launchpad.net:443 uses an invalid security certificate.
The certificate is not trusted because the issuer certificate has expired.
The certificate will not be valid until 04/05/2007 05:03 PM.
(Error code: sec_error_expired_issuer_certificate)

The launchpad pages still appear though, but I had to add an exception for launchpad in order to browse the website.

[Matthew Paul Thomas (mpt)]

Xubuntu 8.04.1 was released on 3rd July 2008, so you must have experienced this problem sometime in the past 27 days.

Therefore, this is not a problem with Launchpad. 25th July 2006, 11th July 2007, and 5th April 2007 are all well before 3rd July 2008, so the certificates were valid by then.

This is, however, two bugs in Firefox. First, the error page apparently does not mention the possibility that your computer's clock is wrong (which seems to be your problem in this case). Second, it falsely claims that "the issuer certificate has expired" when the certificate (apparently) hasn't *started* being valid yet.

[Savvas Radevic (medigeek)]

True, I think it was a clock/cmos battery problem, from what I
remember it was saying "1999" in the date

[John Vivirito (gnomefreak)]

Thank you for taking the time to file this bug report with us. Closing due to age. If this is still a problem in 3.0.7 please reopen this bug.
Also please reopen with all new information on how to reproduce this bug by giving us step by step instructions.
We also need what happens what is expected to happen.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!