| ▲ | indolering 5 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> DNSSEC only protects the name lookup for a host, and TLS/HTTPS protects the entire session. It only provides privacy, it doesn't verify that the resolver didn't tamper with the record. >to the point where the root keys for DNSSEC could be posted on Pastebin tonight and almost nobody would have to be paged. This would very much be a major issue and lots of people would immediately scramble to address it. The root servers are very highly audited and there is an absurd amount of protocol and oversight of the process. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | tptacek 5 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Who? Outside of DNS providers, which organizations would need an emergency response to the collapse of DNSSEC security? Be specific; name one. If TLS security collapsed, I could pick a company from the Fortune 1000 at random, and they'd have an emergency response going. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||