News for hackers. Stuff that matters.
Re:ICANN Calls for DNSSEC for All Domains Following Domain H... by dbrgn on Monday February 25, 2019 @04:22AM (#19244216)
To give an example of how things get better in the real world: Let's Encrypt won't issue a certificate if your DNSSEC records are invalid.
Re:ICANN Calls for DNSSEC for All Domains Following Domain H... by rocqua on Monday February 25, 2019 @04:27AM (#19244247)
Sadly, if you can spoof DNS replies, you can probably strip the DNSSEC records. You need fail-closed systems for security, but fail-closed systems are not user friendly, and thus won't be accepted.
Re:ICANN Calls for DNSSEC for All Domains Following Domain H... by Ajedi32 on Monday February 25, 2019 @10:23AM (#19246221)
> if you can spoof DNS replies, you can probably strip the DNSSEC records

You can't. DNSSEC has explicit protections against that.

Re:ICANN Calls for DNSSEC for All Domains Following Domain H... by rocqua on Monday February 25, 2019 @11:50AM (#19246926)
Those don't work if you claim to be a non DNSSEC compliant resolver. Should clients really fail closed when faced with a non DNSSEC resolver they got from e.g. the starbucks WiFi DHCP? And if they should, do you really think they will? Because users will complain loudly.
Re:ICANN Calls for DNSSEC for All Domains Following Domain H... by Ajedi32 on Monday February 25, 2019 @02:16PM (#19248480)
Clients, no. Certificate Authorities like Let's Encrypt, yes. (And in fact, they already do behave that way.)