Re:A safer and more private browsing experience with Secure DNS
by eatbitseveryday on Tuesday May 19, 2020 @10:50PM
(#23242829)
Hm, why not add an encryption-upgrade path to the protocol using the same port? Why must we use another port?
[ Parent
| on HN ]
Re:A safer and more private browsing experience with Secure DNS
by pas on Wednesday May 20, 2020 @05:51AM
(#23245022)
Again, trivially easy to block that. But DoH is real HTTP(S), you cannot really distinguish it from a HTTPS request for wikipedia.org or outlook.com.
The SNI hole is slowly being addressed by ESNI - https://www.cloudflare.com/ssl/encrypted-sni/