Re:Google Docs will now use canvas based rendering
by EvanAnderson on Wednesday May 12, 2021 @11:03AM
(#27131179)
DNS over HTTPS and, eventually, certificate pinning in the WASM-based DoH client running inside your browser will render your Pi Hole useless. It'll all just be opaque TLS to your network gear. Network operators who legitimately need to control traffic on their networks are lumped in with human rights-violating nation states. That includes you on your network.
[ Parent
| on HN ]
Re:Google Docs will now use canvas based rendering
by dahfizz on Wednesday May 12, 2021 @12:25PM
(#27132115)
Can you substantiate any of that? DoH is a feature of the browser that can be configured or disabled. Firefox even disabled DoH automatically if it detects you are using a custom DNS server which blocks "potentially malicious content"[1].
[1] https://support.mozilla.org/en-US/kb/firefox-dns-over-https
Re:Google Docs will now use canvas based rendering
by EvanAnderson on Wednesday May 12, 2021 @12:44PM
(#27132326)
I'm not talking about the browser doing the name resolution. I'm talking about the opaque binary running inside the browser doing name resolution (either by way of DoH with a pinned certificate, or a custom name resolution protocol running over TLS). You won't get a say in what that opaque binary does (w/o modifying it).
Is anybody doing this now? I doubt it. Will somebody do it? Yeah. Definitely.
When the "browser" is an embedded device (like Google Chromecast devices hard-coded to use 8.8.8.8 for DNS) you'll have no configurability there either.