| ▲ | fulafel 4 hours ago | |
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? | ||
| ▲ | proactivesvcs 3 hours ago | parent | next [-] | |
Other recent submissions include the link to google's blog at https://blog.google/security/chromes-response-to-recent-cctl... : | ||
| ▲ | bsoqk 2 hours ago | parent | prev [-] | |
Nothing novel about this. In fact this is the reason why years ago Google stopped using ccTLDs to serve their website. | ||