Users have reported that 64-bit versions of Firefox are not fully compatible with some anti-virus software. I believe ownership information is only present in Extended Validation certificates, of which this SSL certificate may not be. Firefox will create a functional one afterwards so it is safe to delete it. In which case you could see that the root CA certificate does not belong to verisign.
#How to fix insecure connection for google through firefox windows 10#
The only way this could be someone elses server is if someone redirected your DNS lookup to their server (via DNS cache poisoning or elsewise) AND: So there is a story today about Firefox being deemed too insecure to be part of the Pwn2Own competition. If Firefox is not working on Windows 10 as good as it should check out this article.
Even removed Bitdefender, as I saw online that it may block updated certificates. resetting netsh firewall, ipv6 and dns cache. ADVERTISEMENT The default value of the preference is true, which means that the feature is enabled and that Firefox will display warning prompts when you activate insecure login fields. Attempts I have gone through to connect to Google in Firefox: Changing Date/Time. Load about:config in the Firefox address bar and hit the Enter-key. (2) Adjust to match the current date and time, and click the OK button. If you trust that root certification authority, (ie Verisign via Thawte in the case of Google) then you can trust that the certificate belongs to Google. After updating, Firefox will not connect to Google, saying that it has invalid certificates. To fix your date and time settings, after you close Firefox completely (1) Double-click on the clock on the icon task tray in the bottom right of the screen. As to the validity of the SSL Certificate, so you know you are actually connecting to a google server, you should actually view the certificate itself, and view the chain to the root certificate authority. The content is still transferred encrypted.