News for hackers. Stuff that matters.
Re:nginx: 1-byte memory overwrite vulnerability in DNS resol... by inshadows on Tuesday May 25, 2021 @05:42PM (#27283081)
Like what? Are you going to split the world into two incompatible protocols because of little things like field names?
Re:nginx: 1-byte memory overwrite vulnerability in DNS resol... by zibzab on Tuesday May 25, 2021 @05:45PM (#27283120)
Like a DNSv2 with a more sane encoding scheme.

Given how slow dnssec is being adopted, maybe if we hurry our children can enjoy DNSv2

Re:nginx: 1-byte memory overwrite vulnerability in DNS resol... by tptacek on Wednesday May 26, 2021 @10:24PM (#27298641)
DoH has lots of uptake. So does DKIM. The reason DNSSEC is moribund is that it doesn't solve real problems for ordinary people. I wouldn't be so pessimistic about getting real new stuff deployed.
Re:nginx: 1-byte memory overwrite vulnerability in DNS resol... by inshadows on Wednesday May 26, 2021 @11:13AM (#27291561)
What's insane on DNS encoding scheme? Do you consider binary encoding insane? Would you like to re-engineer protocols down to Ethernet to use JSON? For what reason exactly?

You suggest breaking compatibility for everyone on this planet without giving any specific reason for doing so.

Re:nginx: 1-byte memory overwrite vulnerability in DNS resol... by zibzab on Friday May 28, 2021 @07:20AM (#27314047)
Please read the rfc, then think about how a naive implementation of the name encoding can be abused.

We have had many vulnerabilities related to that single section of the standard over 30 years. At some point you have to ask yourself if the problem lies with the developers or the standard.