Comment #9 on issue 139606 by
rsl...@chromium.org: Invalid Server
Hi Steve,
Right, the behaviour of IE is different because it does not support some of
the enhanced security features in Chrome that are designed to protect users
from attack. Under certain conditions, and based on settings configured by
the site operator (eg:
gmail.com), users are not allowed to override
certificate warnings.
Unfortunately, in some situations, it's impossible to distinguish an attack
from a misconfiguration, which is how you've ended up in this position.
One additional confirmation about your local machine having some form of
misconfiguration or corruption would be attempting to load
https://ssltest15.bbtest.net/ in either Chrome or IE. I would expect, based
on your logs, that it will fail to load.
The Microsoft root program I listed (the social.technet URL) simply has all
of the certificates that are part of the Microsoft root program and the
links to obtain them. To actually install a root certificate, the
directions at
http://technet.microsoft.com/en-us/library/cc754841.aspx can
be used.
Before going too far, I'd try installing the Update for Root Certificates (
http://support.microsoft.com/kb/931125 ). Though it's listed for Windows
XP, I've heard mixed reports that it may run and correct Windows 7.
If it doesn't, however, you'll need to manually install the appropriate
root certificates that have been corrupted in your install. Based on the
URL you're trying to access, I suspect this includes one or more of
the "Equifax Secure Certificate Authority" root certs, which are listed
under the VeriSign column in the Microsoft table. This can actually be
downloaded from
http://www.geotrust.com/resources/root-certificates/index.html - you can
see the Certificate Fingerprint (SHA-1) matches what is listed in
Microsoft's root program.
Downloading and installing this certificate "should" restore connectivity.
As to how your Windows installation got to this point, I'm afraid that may
be a question for the Microsoft forums. As I mentioned, a variety of users
who have filed similar bug reports have found malware as the root cause,
but there may be a wide variety of reasons.