Re:Despite proposed solutions, DNS security issues remain
by tptacek on Wednesday October 10, 2018 @03:08PM
(#18187936)
What about SPF and DKIM? Virtually none of the world's SPF and DKIM records are signed with DNSSEC.
Re:Despite proposed solutions, DNS security issues remain
by amluto on Wednesday October 10, 2018 @07:30PM
(#18189844)
You said:
> The modern Internet was designed with the assumption that the DNS is insecure.
SPF and such may well be designed under the assumption that DNS is insecure but, under that assumption, they too are insecure.
Re:Despite proposed solutions, DNS security issues remain
by tptacek on Wednesday October 10, 2018 @09:48PM
(#18190486)
I don't understand your argument. Again, we have SPF and DKIM now, and neither rely on DNSSEC, which is good, because virtually nobody uses DNSSEC. You absolutely do need SPF and DKIM configured to be a mail sender; the Internet does rely on those. But you do not need DNSSEC to do that, and nobody cares if you do or don't.
Re:Despite proposed solutions, DNS security issues remain
by amluto on Thursday October 11, 2018 @12:18AM
(#18190937)
And the security is weaker than it should be because the SPF, etc records are unauthenticated.
Re:Despite proposed solutions, DNS security issues remain
by tptacek on Thursday October 11, 2018 @12:37AM
(#18191002)
That's not how security works. In the real world, security is in part a resource allocation problem. We spend resources to raise the cost of an attack over the threshold a model attacker would pay. There is a reason nobody gives enough of a shit to sign SPF records, and you can start to see it by taking the time to track down all the incident reports where someone exploited cache poisoning to override SPF.
ARP, and more generally any single-segment Ethernet network, is insecure, and it’s a problem. It’s just a very ingrained problem that’s unlikely to get fixed any time soon.