5 ms·
When Google.com's certificate was faked, it was discovered because Chrome restricts what CAs are allowed to sign Google's certificates, if I recall correctly.
by mortehu 13y ago
When Google.com's certificate was faked, it was discovered because Chrome restricts what CAs are allowed to sign Google's certificates, if I recall correctly.
- tptacek 13y agoGoogle does that for a number of other non-Google sites, too.
- aray 13y agoPretty sure its just google sites, because otherwise you might get false positives as other sites change servers/ips/certificates/etc
- tptacek 13y agoBe less sure. Google provides certificate pinning as a service to other sites, who request it specifically.
- dfc 13y agohttps://src.chromium.org/viewvc/chrome/trunk/src/net/http/transport_security_state_static.json?view=markup https://src.chromium.org/viewvc/chrome/trunk/src/net/http/tr...
- _delirium 13y agoInteresting. Kind of an eclectic small list: Google, Twitter, Tor, CryptoCat.