Closed Bug 896923 Opened 11 years ago Closed 8 years ago

Firefox (18 or 22) refuses to store certificate for *.google.com

Categories

(Firefox :: Security, defect)

22 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: westphal.k.r, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212

Steps to reproduce:

Try to go to ANY google page.



Actual results:

For the past 6 weeks or so, Firefox presents repeates security warnings for ALL Google pages. It tells me that google's security certificate is invalid because it is signed by google. When I try to download the google certificate, I am told it is valid. No permanent storage of a valid security certificate for either *.google.com or for accounts.google.com is possible, no matter what I do with Firefox's security certificates menu. That menu shows certificates for mail.google.com and for www.google.com, but somehow these do NOT work for *.google.com nor for accounts.google.com. The net result is that Firefox makes it EXTREMELY difficult to do normal work on the web, e.g., use my Gmail account, which prior to this worked FINE with Firefox, and which still works FINE with an older version of Firefox on an office computer, and also works FINE from a borrowed Mac with Safari.


Expected results:

Firefox's security certificates MUST be updated so as to allow proper, prompt access to *.google.com and to accounts.google.com. All google web pages should be simple to access.
THANKS for your help!!
Works fine for me on the latest Nightly:
Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20130728 Firefox/25.0

Kenneth, please can you confirm whether this issue still occurs using Firefox in safe mode or with a new profile?

http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Flags: needinfo?(westphal.k.r)
Component: Untriaged → Security
Resolving as INCOMPLETE since there isn't enough information to act on.

Maybe it was a Google issue, anti-virus trying to intercept HTTPS traffic, malware etc.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(westphal.k.r)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.