News for hackers. Stuff that matters.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by krupan on Saturday September 07, 2019 @09:58AM (#20903780)
This! Just like https encrypting website that anyone can visit is not about privacy, DoH is also not about privacy. Anyone can visit the same https website you visit and see what you are reading. Anyone can resolve the same hostnames that you are resolving (or reverse IPs you are visiting to determine hostnames).

The benefit they do provide is authentication (ensure that google.com is really google.com) and protection against man-in-middle.

And those are great benefits!!

But it doesn't help anyone to misstate and/oversell the benefits of a new service/protocol.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by bzbarsky on Monday September 09, 2019 @06:15PM (#20923068)
> Anyone can resolve the same hostnames that you are resolving

Yes, but your ISP (including "that coffee shop whose wifi you're using" in ISP here) can't necessarily tell which hostnames you are resolving, if you use DoH (subject to some limitations about what happens after you've resolved the hostname). This is in fact a privacy feature

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by krupan on Tuesday September 10, 2019 @05:59PM (#20934278)
They can see which IP addresses you go to and do a reverse lookup.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by bzbarsky on Tuesday September 10, 2019 @09:17PM (#20935659)
They can, but of course the mapping is not always 1-1.