News for hackers. Stuff that matters.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by nicolaslem on Saturday September 07, 2019 @03:44AM (#20902405)
> blocking a canary domain

And how long will it take for most ISPs to block this domain when they realize that their DNS servers are not being used anymore? Some of them sell this data so they see it as a source of revenue.

At this point this canary domain will have the same fate as Do Not Track.

> I look forward to applications taking DNS under their own control.

I am sure I can find a hundred applications/programs resolving domains on my machine. It is unrealistic to configure all of them separately. At this point we are back to the OS providing the configuration for all of them.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by GTP on Saturday September 07, 2019 @04:52AM (#20902630)
They already stated in the article that if the canary domain will be abused they will disable that check.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by josteink on Saturday September 07, 2019 @06:38AM (#20902967)
Yeah. Sounds like another do-not-track then.

I’ll keep my firewall-rules banning all DoH-traffic to Cloudflare, just in case.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by Ayesh on Saturday September 07, 2019 @11:42PM (#20908473)
I suppose you can block the IP 1.1.1.1, but Google serves THEIR DNS at `google.com` on HTTPS port. One of the design choices of DoH to make it look like HTTPS traffic.

It's gonna be difficult to block DoH traffic.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by throw0101a on Sunday September 08, 2019 @04:36PM (#20913259)
> One of the design choices of DoH to make it look like HTTPS traffic.

Wait until encrypted SNI gets implemented everywhere was well.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by mtsr on Saturday September 07, 2019 @06:53AM (#20903016)
Not a bad call, I guess.