Earlier quoted context omitted.
They're not threatening to use DNS-over-HTTPS either. But didn't iOS get browser adblocking capability in the last couple years?
Not for third-party browsers like Chrome or Firefox. In a classic Apple-move, it’s for Safari only.
What’s Next in Making Encrypted DNS-over-HTTPS the Default
161–170 of 191 posts
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#162Earlier quoted context omitted.
So now we need to worry about making custom DNS config for every single app on a computer?! It’s absurd.
Does your OS allow you to configure global DNS-over-HTTPS settings? Then you can hardly blame apps for not importing them. Yes, getting rid of shitty old standards means we have to live with multiple in parallel for a while and in the mean time bear additional complexity/work. Otherwise civilization will never advance.
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#163Earlier quoted context omitted.
> DNS is used by ISPs to sell user's data Claims like these keep surfacing in every discussion. While it is good to contemplate what your ISP spying on you would look like and what you can do to minimize that risk, it is not good to present this as normal behaviour. From my perspective I am absolutely certain that this is not something that is routinely done, not in established ISPs in democratic countries. The risks…
How are you so certain that this doesn't happen in general?
Personally I have no idea whether or not this is a common practice, though I have to agree with xorcist that it's certainly not a given.
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#164Earlier quoted context omitted.
They already stated in the article that if the canary domain will be abused they will disable that check.
Yeah. Sounds like another do-not-track then. I’ll keep my firewall-rules banning all DoH-traffic to Cloudflare, just in case.
It's gonna be difficult to block DoH traffic.
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#165Earlier quoted context omitted.
I guess thats Mozillas new monetizing strategy, sell user data to cloudflare, and market it as privacy. If you want privacy you better firewall everything your computer want to send to Cloudflare, Akamai, et.al.
Good luck with blocking Cloudflare and Akamai and still using the internet.
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#166I use DoH on Firefox and love it but man, I myself would block Firefox in a corporate network I help oversee if this is the default. Matter of fact, web proxies already list DoH resolvers as anonymizing sites.
Even if this involves some profit with cloudflare,this is strategically terrible for long term goals.
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#167Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#168Earlier quoted context omitted.
And DNSSEC all the way to the user!
I'd be pretty pissed if my network connection opted me into a DNSSEC-verifying resolver, since that is pretty much pure downside for users.
Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#169So what will be « safer » ? Using a pi-hole or equivalent, or using this ? IIRC all DoH requests are sent to Cloudflare. Is there a way to host your own DNS server and use it with DoH instead ?
Yeah, you can re-configure Pi-Hole to use DoH (with your preferred servers). unbound can be configured to use DoH as well.
local-zone: "use-application-dns.net" staticRe: What’s Next in Making Encrypted DNS-over-HTTPS the Default
#170Earlier quoted context omitted.
I'd be pretty pissed if my network connection opted me into a DNSSEC-verifying resolver, since that is pretty much pure downside for users.
As someone not very knowledgable about DNSSEC, can you expand on this point? To the uninformed that sounds very counterintuitive.