8 ms·
Google rolls out DNS-over-HTTPS support in Chrome 83
- sasasassy 6y agoI wonder in what new ways will ISPs start blocking illegal websites.
- bilegeek 6y agoCouldn't they just block the IP? Sure, it's easier to get a new IP than a new URL, but still?
- realusername 6y agoWhen a good chunk of websites are behind Cloudflare, hosted on AWS or on another cloud platform, the IP is increasingly useless.
- tupuc_speedrap 6y agoCan't wait for Google to be named "Internet Villians" like Mozilla because GCHQ got salty they can't slurp DNS traffic.
- throw0101a 6y agoIt wasn't GCHQ, it was UK ISPs: * https://www.theregister.co.uk/2019/07/06/mozilla_ukisp_vallain/ https://www.theregister.co.uk/2019/07/06/mozilla_ukisp_valla... They have (had?) a requirement to block certain sites (e.g., CP), and their CEOs could be sent to jail if they didn't. So from their perspective, Mozilla was not doing a good thing as it was causing them grief in being able to follow the law: > for their proposed approach to introduce DNS-over-HTTPS in such a way as to bypass UK filtering obligations and parental controls, undermining internet safety standards in the UK * https://www.ispa.org.uk/ispa-announces-finalists-for-2019-internet-heroes-and-villains-trump-and-mozilla-lead-the-way-as-villain-nominees/ https://www.ispa.org.uk/ispa-announces-finalists-for-2019-in... So yeah, I can understand why they'd be salty. As someone who works in IT I'm also salty at DoH for similar netsec reasons. (DoT is another matter.)
- Avamander 6y ago> It wasn't GCHQ, it was UK ISPs With UK laws it's close enough.
- kashug 6y agoIsn't the most common way to block "illegal websites" just to block it on the DNS owned by the ISP? (which is the one you will automatically use unless you configure something else). And just making their domain point to some website saying the site is blocked. Afaik this will still work. And the normal workaround of just changing to a different DNS should work aswell. Is sniffing of traffic common in other countries?
- throwaway8941 6y agoI don't know about other countries, but this never worked in Kazakhstan. They block whole IP ranges and your traffic silently gets dropped. I'm sure that having a single monopolistic ISP helps with implementing this.
- sasasassy 6y agoI think that this change would mean that, by default, the DNS server used will be specified by Google/Chrome team. If the DNS server were still my router then there's no point to this really.
- dingaling 6y ago> the DNS server used will be specified by Google/Chrome team I don't think that any oppressive regime is going to have any qualms about routing 8.8.8.8 to its own server, or just blocking it. So you use the national DNS or get nothing.
- dekrg 6y agoThey will do nothing and wait for new and stronger censorship and anti-encryption laws. After which HN dudebros will act all surprised and confused as to why countries don't simply accept techbros circumventing their laws.
- mrtksn 6y agoIn Turkey, It's DNS + IP blocking. There are rumours for slowing down certain connections, especially social media stuff when something sensational happens.
- anticensor 6y agoMore actually. Many levels of blocking exist but not all actively used. Different websites are blocked using different methods at different levels.
- mrtksn 6y agoCorrect. However, I believe it's not because the government mandated it. The same website could be blocked differently on different ISPs. For example, when Wikipedia was blocked it was not possible to access it without a VPN from Kablonet but a simple DNS provider change was enough on TurkNET.
- anticensor 6y agoTurkcell implements the most powerful censorship and Turk Telecom has the most sophisticated censorship infrastructure in Turkey.
- mrtksn 6y agowhat's the difference between powerful and sophisticated censorship mechanisms?
- anticensor 6y agoThe sophisticated one is distributed and also more resilient against workarounds, the powerful one is centralised yet has the ability to process most requests per unit time without visible degradation on connection speed and latency.
- throw0101a 6y agoBlackhole routing. You setup a /dev/null router with BGP and advertise the IPs you want unreachable, and things get dropped at the network edge. IMHO, DoH will simply have network operators go from having a light touch on the network with DNS filtering, to a much heavier hand with routing and inspection. Because the regimes and laws that are currently in place won't just magically go away. (Thanks Mozilla.)
- mrweasel 6y agoI doubt they would do blackhole routing, they risk blocking IPs from cloud providers like AWS, Azure and GCP. Perhaps it's a little naive of me to think that ISP and government would consider that they might block and IP that's only going to do something "illegal" for a short while and the be recycled for something else.
- tialaramex 6y agoThe intent is that collateral damage from such actions is so enormous that they become unthinkable. "We'll just block all of Cloudflare's IPs" is like "We'll just ban all Chinese products". OK, so now your economy is in ruins, what next? China's great firewall for example degrades access to some popular web sites, but it doesn't do a lot of IP blackholing because that hurts China more than they'd like.
- syshum 6y agoThe idea that authoritarian regimes will just say "ohhh know it is cloudflare" and then back down is extreme naive More likely they will just force Cloudflare to do their censorship for them, which cloudflare has already been proven to be malleable toward
- throw0101a 6y agoThey don't have to block all of Cloudflare's IPs. First they block 1.1.1.1 so that DoH doesn't work, then they look at" 'nown bad' domains and see to what they resolve to and start with those. If there's collateral damage to some other sites, then depending on the 'importance' of that they want to block--oh well.
- Dolores12 6y agoHow will that affect things like pi-hole?
- dogma1138 6y agoI have Pi-Hole configured to use DoT for it’s outgoing DNS requests in a home network with a DNS server you trust using DoT internally is arguably less important. I’ll be looking to see if what configuration options are available and if I can set up a DoT server on the Pi-Hole. Ideally I would want at least the ability to set DoT on/off by default based on the network I’m using so if it’s the home network I don’t care but all other networks I would like to have DoT as the default option. It would also be interesting to see if there is a default fallback unto standard DNS or not.
- ajphdiv 6y agoSetting up recursive dns with unbound on the pi-hole https://docs.pi-hole.net/guides/unbound/ https://docs.pi-hole.net/guides/unbound/
- rndomsrmn 6y agoSee: https://github.com/notracking/hosts-blocklists#dns-over-https-doh https://github.com/notracking/hosts-blocklists#dns-over-http... how Mozilla deals with this. For Chrome this feature seems not to be implemented, making it harder to control your DNS behavior in your own network. (see Q&A at the bottom of the page) https://sites.google.com/a/chromium.org/dev/developers/dns-over-https https://sites.google.com/a/chromium.org/dev/developers/dns-o...
- donatj 6y agoThe subsequent SSL requests still include the host in clear text, so while a move in the right direction, does little to stop request sniffing.
- svenfaw 6y agoNo, they only include the DNS server name in cleartext. (Unless I’m misunderstanding DoH)
- donatj 6y agoThe lookup is encrypted yes. Your actual subsequent request to the webserver you looked up the DNS entry for however exposes the host in clear text. This is how a lot of corporate firewalls sniff HTTPS requests for host without a root cert. https://security.stackexchange.com/questions/86723/why-do-https-requests-include-the-host-name-in-clear-text https://security.stackexchange.com/questions/86723/why-do-ht...
- terinjokes 6y agoIf you enable it in about:config, Firefox does support the Encrypted SNI proposal when used with DoH and providers that support it. It works for me on Firefox for Android. https://blog.cloudflare.com/encrypted-sni/ https://blog.cloudflare.com/encrypted-sni/ Disclaimer: I work for Cloudflare, but not on this project.
- livre 6y agoESNI is a great solution but unlike DoH it has yet to see wider adoption. I have it enabled and I have Firefox pointed to my local DoH server, the majority of the websites still reply with NXDOMAIN to the _esni query. Besides Cloudflare I've only found 1 other website that has it enabled.
- aquadrop 6y agoYou still ultimately will be exposing server you're talking to by ip, right?
- jgaa 6y agoSo, then google get to decice what web sites that even exist in your universe. Nice played.
- kreetx 6y agoChoose another DNS server.
- detaro 6y agoChrome checks if the DNS server configured supports DoH, and if yes uses DoH to talk to it. How exactly does that mean that > google get to decice what web sites that even exist in your universe.
- jedimastert 6y agoI see you read the article... \s
- talliedthoughts 6y agoRunning version 83.0.4103.61 but I don't see the DoH-related entries in Chrome Settings. Is this still in a phased rollout?
- bfoks 6y agoOption is visible under chrome://flags/#dns-over-https flag. However on Ubuntu 18.04 I've the message: "Not available on your platform.".
- cornedor 6y agoSame here, same version. I also do not have the new Safety Check described here: https://www.blog.google/products/chrome/more-intuitive-privacy-and-security-controls-chrome/ https://www.blog.google/products/chrome/more-intuitive-priva...
- DavyJone 6y agoIsnt this something the OS should handle and Chrome just uses the OS interfaces for this?
- afandian 6y agoThis has echoes of MS SQL Server (and maybe others) where there's an argument to built a miniature operating system within RDBMS for technical reasons. Given that whole UI and windowing toolkits are moving into the browser, that argument of replacing chunks of the OS, from top to bottom, starts to become more relevant (if not more comfortable). And then the next step could be to have Google as a compulsory proxy for all web traffic, because of government blocks.
- majke 6y agoIsn't TLS 1.3 something OS should provide? Isn't QUIC something an OS should provide? Isn't the OS responsible for preventing antivirus software installing insecure browser plugins? Isn't the OS responsible for process sandboxing? Isn't the OS responsible for secure font rendering? Isn't the OS responsible for shipping with decent optimized image and movie decoding libraries? The innovation must be pushed somewhere. These days it's being pushed by the browser vendors and not OS vendors.
- DavyJone 6y agoYep and not saying its entirely wrong, but check my reply to asdf-asdf-asdf.
- asdf-asdf-asdf 6y agoin theory, yes. the problem is, how can chrome+firefox persuade microsoft, apple, debian and redhat to add it? and how long will that take? maybe some of them don't want it at all. with the current approach they can offer this improvement to their user right now.
- DavyJone 6y agoI understand that, but what Im concerned about is Chrome or Firefox or etc skipping my OS settings and preferences. Like they already do in some cases.
- dijit 6y agoDoH is such a weird concept to me. It feels like HTTP is a pretty poor protocol to be eating the world. I can easily imagine that the resources being spent on DoH are many orders of magnitude more than was spent on actually fixing or updating the DNS protocol. This is not in defence of the current DNS system, I'm just sad that the only way we can think to fix DNS is to make it not DNS, but some form of HTTP name resolution.
- mytailorisrich 6y agoThere is no DNS-related reason to use HTTPS. This is a tactical move to obfuscate and make port filtering more difficult because suddenly DNS uses the same protocol and same port as 99% as your traffic. This is versus DNS-over-TLS that offers the same privacy BUT still uses a DNS-specific port so is easier to detect and block. Of course you can still block by IP... Other than that, it is exactly the same DNS messages. It's just that they are encoded in HTTP messages.
- kees99 6y agoI think you're right on the money here. DNS-over-TLS uses port 853, so is trivial to block on a firewall and force fallback to plain-text DNS. DoH is resilient to such an attacker - be it sketchy guy in starbucks trying to steal your cookies, or yourself trying to run pi-hole adblock.
- dijit 6y agoNot sure why you couldn't do TLS over port 53 though, we've had STARTTLS for decades, you can even inform software not to fallback. The downside is, of course, that Starbucks can't redirect you to their "please accept our TOS" portal.
- deleted 6y ago[deleted]
- mytailorisrich 6y ago
- csdreamer7 6y agoDoes this ignore the os hostfile like Firefox's DoH does?
- nickcw 6y agoFor those of you worrying about what this will do to parental controls, I did a little bit of research. In this blog the chromium team say: https://blog.chromium.org/2019/10/addressing-some-misconceptions-about.html https://blog.chromium.org/2019/10/addressing-some-misconcept... > The first claim is that Google is going to redirect user DNS traffic to Google's own DNS or another DoH-compliant DNS provider. That is incorrect. Because we believe in user choice and user control, we have no plans to force users to change their DNS provider. Today, there are many independent DNS providers, although ISPs serve approximately 97% of user DNS needs. As long as these service providers keep catering to user needs and concerns, it will remain a diverse ecosystem. We’re simply enabling support in Chrome for secure DoH connections if a user’s DNS provider of choice offers it. Chrome will check if the user’s DNS provider is among a list of participating DoH-compatible providers and if so, it will enable DoH. If the DNS provider is not on the list, Chrome won’t enable DoH and will continue to operate as it does today. As DoH adoption increases, we expect to see the number of DoH-enabled DNS providers grow. This is re-iterated in the next paragraph > The second claim we’ve seen is that the secure DoH connection will limit the family-safe content controls offered by some ISPs. In fact, any existing content controls of your DNS provider, including any protections for children, should remain active. DoH secures the URL data only while it’s in transit between your browser and the DNS provider, so your provider’s malware protection and parental control features will continue to work as they have in the past. So this isn't going to break parental controls by default... ...unlike Firefox's proposed scheme which requires action by the DNS providers. https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https https://support.mozilla.org/en-US/kb/configuring-networks-di...
- lol768 6y ago>...unlike Firefox's proposed scheme which requires action by the DNS providers. Maintaining a hardcoded whitelist of providers (which is what it sounds like is happening in Chrome) is a bit naff. Mozilla's solution scales, at least. Also, their solution doesn't _require_ action from the DNS providers - corporate IT staff can customise this behaviour for managed machines via an pref or enterprise policy. Defaulting to transport security for DNS queries out of the box is a Good Thing.
- ck2 6y agoit still obeys HOSTS right? have to assume that's a must eta: oh interesting, at some point I turned on "managed" to prevent it from password cloud saving or some other nuisance and now I get this: Use secure DNS This setting is disabled on managed browsers
- foodscraps 6y agoI use PiHole with a DoH upstream. I want all devices on my network to use my DNS server. Mozilla's implementation is easily managed using their canary domain "use-application-dns.net" but Google doesn't have this option. I do not want any queries sent to Google. It is not feasible to manage chrome flags on every device, especially mobiles. Does anyone know if Chrome will be using their two public IP's, 8.8.8.8 and 8.8.4.4 for this new DoH service? If that is the case this will be easy to block at the network level. Thanks.
- Kalium 6y agoChrome Enterprise (which, contrary to what the name might suggest, is not a paid enterprise offering) offers management tooling for managing flags across many devices. Here's the flag for DoH: https://cloud.google.com/docs/chrome-enterprise/policies/?policy=DnsOverHttpsMode https://cloud.google.com/docs/chrome-enterprise/policies/?po...
- propogandist 6y agobut Chrome Enterprise means it has to connect and phone home to Google all the time anyway, no? That defeats any potential benefit of having more control over the browser. Given this is a "free" offering, the data being mined finances this service.
- Kalium 6y agoIf parent wants to manage Chrome configuration across N devices, Chrome Enterprise is a good tool for the job. They may or may not care if their data is on Google servers or not. They might consider these two items to be two entirely distinct and different benefits. If parent wants to avoid having any of their data cross Google machines, you are completely correct that Chrome is the wrong tool for the job.
- codecasaurus 6y agoHave you considered just blocking outgoing on port 53 on your network? There are a few too many devices out there that have hardcoded DNS and don't respect the resolver communicated to it. (Chromecast is an easy example.)
- newman314 6y agoFWIW, this seems to be the GPO that controls DoH https://cloud.google.com/docs/chrome-enterprise/policies/?policy=DnsOverHttpsMode https://cloud.google.com/docs/chrome-enterprise/policies/?po... I was looking for this as I want to explicitly control when I choose to enable DoH.
- someonehere 6y agoSo if I wanted to keep analytic data of where my users are going, should I set up my own office DoH server and forward requests to an external DoH? Would I be able to then use our in house DoH and get analytics from that?
- ancorevard 6y agoIs this a scheme from adcompanies like Google to circumvent Pi-hole?
- jpalomaki 6y agoMaybe not. Dns over http makes it easy to use for example http://nextdns.io http://nextdns.io which is nice alternative for Pi-hole (and more convenient IMHO). I think this is mostly against ISPs who would like to mess with/redirect your traffic (for example show their own page for mistyped URLs).
- ric2b 6y agoPi-hole can just support DoH as well, this doesn't really change anything in terms of adblocking.
- dekhn 6y agoi'd rather have https over dns, to deal with wifi portals.