4 ms·
You'll still be able to run your own resolver that applies DNS filters and configure your client to use it, just like today. The difference will be that connec
by agwa 7y ago
You'll still be able to run your own resolver that applies DNS filters and configure your client to use it, just like today. The difference will be that connections between the client and the resolver will be secured with HTTPS, so your DNS can only be tampered with and surveilled if you give consent. That seems like a win for user freedom to me.
- throwaway2048 7y agoThis is only true if devices and programs don't use pre-baked in DoH servers, like chromecast currently is.
- agwa 7y agoThe Chromecast has always been a locked-down device. I suppose it's frustrating if unsecured DNS was the one way that you could exert some control over a device that isn't truly yours, but that's just not a battle than can be won. Your beef should be with the Chromecast, not DoH.
- belltaco 7y agoChromecast could also switch to using a new custom encrypted protocol that no one else understands or can decrypt to communicate with Google servers and funnel IP lookups through it, regardless of DNS or DoH. You cannot fight and circumvent such malware already present in software and hardware that you bought or installed.
- TeMPOraL 7y agoTrivial inconveniences matter. The easier it is to act malicious, the more software will.
- JohnFen 7y ago> You'll still be able to run your own resolver that applies DNS filters and configure your client to use it, just like today. Not really, because you have no way to enforce the use of your own resolver or filters without using a proxy to MITM your HTTPS connections.