Closed Bug 562098 Opened 14 years ago Closed 14 years ago

Possible incorrect expired certificate notice for gmail.com or google.com

Categories

(Firefox :: Security, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: liz, Unassigned)

Details

Forwarding a report (sent using the form for reporting trademark infringement) that seems to say there's an incorrect expired certificate notice for gmail.com or google.com, though I can't really tell if that's what whoever sent this was trying to tell us. No need to keep me in the loop, I'm just passing this on in case it's something that should be acted on. I can't answer any questions and there's no record of who sent it.

A new violating website report has been submitted with the following information:

+ URL
http://www.gmail.com

+ Category
Charging for software

+ Product
Firefox

+ Specific product
+ None

+ Trademarks
Firefox

+ Modified Mozilla product?
+ None

+ Other details...
www.google.com uses an invalid security certificate.

The certificate will not be valid until 12/18/2009 5:30 AM.

(Error code: sec_error_expired_certificate)

+ Attachments...
+ None
(In reply to comment #0)
> Forwarding a report (sent using the form for reporting trademark infringement)
> that seems to say there's an incorrect expired certificate notice for gmail.com
> or google.com, though I can't really tell if that's what whoever sent this was
> trying to tell us. No need to keep me in the loop, I'm just passing this on in
> case it's something that should be acted on. I can't answer any questions and
> there's no record of who sent it.

> + Other details...
> www.google.com uses an invalid security certificate.
> 
> The certificate will not be valid until 12/18/2009 5:30 AM.

thanks for filing, but that message indicates that the repoter's clock was just bad - 2009 is in the past, but this is a "not yet valid" message, so yeah - bad clock.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.