5 ms·
You don't get to control what my devices do just because you control a network they're transiting through. Even if DoH had never been standardised, clearly my d
by tialaramex 5y ago
You don't get to control what my devices do just because you control a network they're transiting through. Even if DoH had never been standardised, clearly my devices can do this anyway.
On the other hand, if you actually control your devices DoH shouldn't be a problem, you can have them talk to whichever servers you prefer regardless of the protocol.
As to the lightweight thing. We get a few benefits from running DNS on top of HTTPS rather than say TLS (which also exists, as DoT)
1. HTTPS allows us to put parameters in the URL which are thus confidential (HTTPS will encrypt them) and have those control the DNS lookup. So dns-server.example can offer all its users their own URL, even though they all talk to the exact same server (dns-server.example.com) and a snoop can't tell that one device used the rank0 account while another device used the tialaramex account, those are encrypted in the URL, yet the actual server can see which is used and maybe my devices get "pure" answers while yours have ad-blocking or whatever.
2. DNS doesn't have a rich error vocabulary. For your ad-blocked domains, a traditional DNS server has to either lie (bogus answer) or claim no answer exists (NXDOMAIN or OK 0 answers) but HTTP has a rich variety of error codes. Maybe 403 Forbidden is appropriate for the Xian parent who doesn't want their teenager looking at pornhub.com and 451 Unavailable For Legal Reasons is appropriate for a DNS service which excludes Pirate Bay due to lawsuits.
- akersten 5y ago> You don't get to control what my devices do just because you control a network they're transiting through. And if I run a guest wifi in one of the many countries where I have legal obligations to take steps to block illegal traffic because I am ultimately responsible for the emissions of my network, what would you suggest I do? > DNS doesn't have a rich error vocabulary. For your ad-blocked domains, a traditional DNS server has to either lie (bogus answer) or claim no answer exists (NXDOMAIN or OK 0 answers) but HTTP has a rich variety of error codes. It's a good thing that DNS has a limited vocabulary of error codes. I want the garbage website to think it couldn't load the ad because of a mysterious DNS issue. Having a reason like "DNSHTTP 486: Blocked by Client" would just make it that much easier for the site to deny you access/track you/detect your blocking activity.
- stinkytaco 5y ago> And if I run a guest wifi in one of the many countries where I have legal obligations to take steps to block illegal traffic because I am ultimately responsible for the emissions of my network, what would you suggest I do? This is an oft overlooked part of these discussions. I manage a public network at a library (which is still the only access point for many people, unfortunately). DNS blacklisting certainly isn't the only tool in the toolkit, but it is one that DoH takes out. I'm genuinely conflicted on DoH because on one hand, I am a privacy advocate, but on the other I run a public network and that comes with certain obligations, both legal (we need to block filesharing) and to customers (we do traffic shaping because the budget it limited and bandwidth isn't cheap).
- SilverRed 5y agoYou do what every company does. Deploy industry standard methods and record your processes. And then when someone comes asking, you show them you did everything right and that is usually the end of it.
- stinkytaco 5y agoThat's not the case in the US. Our ISP will absolutely be within their rights to cancel our service if someone on our network is violating their TOS. And we don't really have the money or the standing to fight it.
- tialaramex 5y agoAs with steps someone might have a legal obligation to take to prevent people from thinking negative things about the King or to prevent six from being an even number, you should do whatever you feel is appropriate. It might even make a difference. Perhaps you could put up a notice which says "I run guest WiFi here and I have legal obligations to block illegal traffic so, don't do anything illegal". It's certainly weird to insist it's everybody's else's problem that you're subject to legal obligations that may be impossible to fulfil. If the purpose of this "obligation" is to ensure nobody is technically compliant and so they can arrest, imprison or even execute whoever they want, it doesn't seem like that's my fault, or Mozilla's fault, or any of the authors and acknowledged contributors for RFC 8484. Any more than it's Giuseppe Peano's fault that six is even. And if (as seems most likely) they're just covering their backside, the notice is probably sufficient.
- dogecoinbase 5y ago_You_ are not in control of _your_ devices. Your television will use this technology to report what shows you're watching to the company that manufactured it; the web browser running on your computer will use this technology to report your activity and retrieve advertisements even if you've tried to block them elsewhere.
- iso1210 5y agoIt amazes me how people think the worlds largest advertising company is pushing DoH out of alturism. That pihole you're running? That 'steals' money from google. DOH gets rid of that.
- josephcsible 5y agoYou can still use ad blocking with DoH. Just pick a DoH server that does so (or run your own) instead of using the default one. Or just use a browser extension like uBlock Origin instead. Nobody's trying to kill your Pi-hole with DoH. They're trying to kill your Pi-hole by serving ads from first-party domains.
- depingus 5y agoYou missed the point. OP is talking about app and IoT devs hard coding DoH servers into their products so that they can bypass any tracking, advertising, and privacy restrictions (aka piHole) you put in place.
- josephcsible 5y agoDevices like that could just hardcode the IP addresses of their ad servers instead, so DoH isn't really the culprit there.
- Spivak 5y agoYeah there’s nothing about DoH that a Google or any IoT device maker couldn’t have done 10 years ago if they really wanted to bypass local DNS servers.
- iso1210 5y agoYou want to use my network you live by my rules. You don't have to connect to it.
- SilverRed 5y agoSo don't let untrusted devices on your network. Once they are on the network they are able to do anything you don't block.
- throw0101a 5y ago> On the other hand, if you actually control your devices DoH shouldn't be a problem, you can have them talk to whichever servers you prefer regardless of the protocol. I already do tell the devices I control which DNS servers to use via DCHP and IPv6 RA. Firefox is choosing to ignore that by default, and now I have to go through extra steps to solve a problem that Mozilla created by not simply re-using the previous solution (gethostbyname(3)). At the very least if they had simply used the already existing DoT, instead of inventing a new protocol (DoH), I could have monitored port 953 traffic and see which devices were broken. Now I have to figure out devices trying to sneak through my policies.
- josephcsible 5y agoIt's good that they didn't use DoT, because then it would be too easy for adversaries who want to do censorship or surveillance to just block port 853.
- throw0101a 5y agoDo you think that DoH prevents adversaries from doing censorship and/or surveillance? > DoH encrypts precisely zero data that is not already present in unencrypted form. As it stands, using DoH only provides additional leaks of data. SNI, IP addresses, OCSP and remaining HTTP connections still provide the rest. It is fake privacy in 2019. * https://twitter.com/PowerDNS_Bert/status/1175744071673028608 https://twitter.com/PowerDNS_Bert/status/1175744071673028608 In the resulting HTTPS web request you have the hostname anyway. Think that ESNI will save you? Well that's being blocked: * https://www.theregister.com/2020/08/11/china_blocking_tls_1_3_esni/ https://www.theregister.com/2020/08/11/china_blocking_tls_1_... * https://www.zdnet.com/article/dns-over-https-causes-more-problems-than-it-solves-experts-say/ https://www.zdnet.com/article/dns-over-https-causes-more-pro...
- glennpratt 5y agoSounds like eSNI is a good move if China is blocking it.