News for hackers. Stuff that matters.
Re:DNS Privacy Considerations by Havoc on Saturday July 31, 2021 @07:20AM (#28017112)
This whole area is an absolute harrowing rabbithole. Even just DoH never mind ESNI

When you think you've got a grip on it there are leaks. pihole and cloudflared tunnel set up? Nope FF just bypasses it. Something still leaking? oh that's ipv6. Still no good? Oh DNS can bypass your port 53 firewall rule cause udp fallback. etc etc.

Oh and good luck testing it. Different results in FF/Chrome/Edge...and sometimes even variability between tests per browser. Hows that even possible with 53 FW blocked? No idea

Re:DNS Privacy Considerations by donmcronald on Saturday July 31, 2021 @01:31PM (#28020070)
IMO the current effort isn't about improving privacy or reducing censorship or a battle to stop tracking. It's a battle for who gets to track you. Winning market share in the DoH space is the same as winning the ability to control one of the only hops where users can be tracked.

I think it's worse than having a ton of crappy ISPs doing DNS. Yeah, they probably sold my data to shady businesses, but DoH has the potential to be a much better mass surveillance and censorship system. Is it easier to get a US court order for Cloudflare and Google to block the pirate bay via DNS or to get 1k court orders from 1k jurisdictions around the world?

And the "benefit" we're going to get as users is un-blockable ads because that's the ultimate goal of DoH. Instead of my Roku trying to use 8.8.8.8 it'll use some DoH server at a CDN that's hard/impossible to block.

They're literally building the next generation surveillance / censorship system and selling it to us as "for your protection".

Re:DNS Privacy Considerations by ViViDboarder on Saturday July 31, 2021 @05:31PM (#28021728)
> And the "benefit" we're going to get as users is un-blockable ads because that's the ultimate goal of DoH. Instead of my Roku trying to use 8.8.8.8 it'll use some DoH server at a CDN that's hard/impossible to block.

Can you not set the DNS server just as you do today? Or are you rewriting the IP for 8.8.8.8 to a private server and worried that HTTPS will prevent this?

Re:DNS Privacy Considerations by donmcronald on Tuesday August 03, 2021 @03:53PM (#28053343)
I think 8.8.8.8 is hard coded somewhere in those devices. I can’t remember exactly how it worked, but it’ll ignore the dhcp assigned dns sometimes.

With DoH it’ll be impossible to block and I think there’s a good chance they’ll flat out ignore local dns at that point.

Re:DNS Privacy Considerations by netr0ute on Saturday July 31, 2021 @09:37AM (#28018019)
That's why you block port 53 in both UDP and TCP so nothing can bypass it. I also block most known DoH servers outright.
Re:DNS Privacy Considerations by tremon on Saturday July 31, 2021 @10:28AM (#28018424)
I also block most known DoH servers outright.

When someone hosts a DoH server on a cdn/AWS/Azure/Google shared IP address, you can't block it by IP; and if the client uses ESNI, you can't block it by HTTP header inspection either.

Re:DNS Privacy Considerations by netr0ute on Sunday August 01, 2021 @06:25PM (#28030739)
How will the client know what address to send DoH to? You wouldn't just hardcode an IP unless you want that predictable address manually blocked in the firewall.
Re:DNS Privacy Considerations by silon42 on Saturday July 31, 2021 @10:18AM (#28018334)
Also need to block all hosts not allowed by your own DNS server. Also need to give each "untrusted" app a separate local IP (in future: must have NAT for IPv6 too).
Re:DNS Privacy Considerations by silon42 on Saturday July 31, 2021 @10:29AM (#28018435)
Or just force the use of HTTP/S proxy.
Re:DNS Privacy Considerations by Havoc on Saturday July 31, 2021 @11:06AM (#28018739)
>That's why you block port 53 in both UDP and TCP so nothing can bypass it.

Already done...something is still sneaking through...or cloudflares test is unreliable (or my iptables rules are wrong lol)