↑
logo

Hackers obtain counterfeit TLS certificates for Google and other large services

Posted by colinprince |2 hours ago |5 comments

Borealid 43 minutes ago

This sounds like something that HPKP ( https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning ) could have prevented and CAA records ( https://letsencrypt.org/docs/caa/ ) could not. But HPKP is deprecated.

rswail 43 minutes ago

The affected country ccTLDs are:

AS: American Samoa

GH: Greenland

SL: Sierra Leone

an hour ago

Comment deleted

netik 37 minutes ago

This seems like bullshit given certificate pinning and other countermeasures here. What am I missing ?

Is it TLDs lacking support for this?

aiXis 25 minutes ago

[flagged]

fulafel 2 hours ago[1 more]

From the Google blog "Chrome's Response to Recent ccTLD Registry Hijacks":

"These incidents did not involve a compromise of Google’s systems; rather, attackers compromised the third-party ccTLDs, putting any domain ending in .gh, .sl, or .as at risk. During these hijacks, attackers modified authoritative DNS records and obtained unauthorized HTTPS certificates covering several Google domains, as well as domains belonging to other organizations."

So entire top level domain registries were compromised. Interesting times. Isn't there really any primary source on this?