The project especially lists the problems of TLS. TLS is one of the most understood, tested, and well-defined protocols that can be abstracted away in implementation level. Nothing also prevents forcing TLS 1.3 which removes most of the described other problems.
This especially sounds odd:
> Questionable practical benefits over DoH
But DoH brings the full TLS stack and also the HTTP stack as well? At the same time the project complains about increased attack surface in DoT, but DoH just extends it even more.
If I also look the DoH list, there is
> Requires TCP
But just few lines befeore, they say that DoH supports HTTP/3 which is UDP.
E.g. Android has supported it 3 years already:
https://security.googleblog.com/2022/07/dns-over-http3-in-an...
> The project especially lists the problems of TLS. TLS is one of the most understood, tested, and well-defined protocols that can be abstracted away in implementation level.
I agree that TLS is understood, tested, used every day etc. I do not agree that you sleep calm at night. For example a few years ago [1] or [2] mozilla removed root CA from firefox for bad behavior. And you can argue everything is working properly because bad behavior was detected and removed but the thing is - you can avoid this group of problems entirely by avoiding PKI in protocol. That is why I like dnscrypt protocol more. Less problems to worry about. You only change hardcoded/configured public key if you change which dns server you are using (not a big deal). You do not have to regularly update router to keep root ca store up-to-date. Do you update your router every month? Because I do not.
[1] https://www.feistyduck.com/newsletter/issue_53_certificate_a...
[2] https://www.itbrew.com/stories/2022/12/02/mozilla-microsoft-...
This is plain false: https://en.wikipedia.org/wiki/European_commision
Are they using nsd or bind or … did they write their own?
and there is also 9.9.9.10, which does not perform any blocking (if it does, then no one has noticed that, which is unlikely)