News for hackers. Stuff that matters.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by Jonnax on Saturday September 07, 2019 @03:20AM (#20902322)
There's a lot of negativity here.

But this is a win overall for privacy.

DNS is used by ISPs to sell user's data and is one way that oppressive regimes track what their users do.

If you're technical enough to understand DNS then you are smart enough to change what the default is.

If you're a system administrator for a company. You should be able to push a profile down to the user's computer to configure DNS how you want.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by xorcist on Saturday September 07, 2019 @06:56AM (#20903028)
> 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 would be far too great for a tiny income. Who would you sell to? The advertising networks have their own data sources, and even the web giants with billions of users and trackers embedded in pretty much every web page you visit can't charge much.

Even if you wanted to do this, DNS would be a low value target considering it is cached at every layer. Data mining sFlow logs, which is something every ISP would use anyway for diagnostic purposes, would give you better view of which kind of services users connect to and for how long.

So please don't normalize something that is at best a niche for bad actors. That can lead to decisions for end users, many of whom would be wiser not sending their data off to a foreign third party.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by BubRoss on Saturday September 07, 2019 @06:14PM (#20906944)
How are you so certain that this doesn't happen in general?
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by Ajedi32 on Saturday September 07, 2019 @11:17PM (#20908395)
Is there any evidence suggesting that it does?

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 by BubRoss on Sunday September 08, 2019 @05:26PM (#20913528)
It is common for AT&T
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by throw0101a on Sunday September 08, 2019 @08:55AM (#20910276)
> DNS is used by ISPs to sell user's data and is one way that oppressive regimes track what their users do.

Your ISP may do this, but mine does not, so why should Mozilla get to dictate IT policy of my machine (i.e., ignoring resolve.conf)? Or policy of the company where I help run IT?

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by Jonnax on Monday September 09, 2019 @04:29PM (#20922116)
DNS is a plaintext protocol. It's a new technology. Technically this is better.

It reminds me of this silliness I sometimes hear:

"I need to use NAT with IPv6 to protect my network"

Firefox will allow you to set up a DNS rule locally that forces the client to use local dns, if you need it.

You can also configure a DNS over HTTPs server as your DNS.

If you help run IT and care about security. Then you should be blocking direct access to the internet anyway.

All your traffic should be going through a proxy server.

Also defaults should help those that are in weaker security positions. Just because you're lucky to have a good ISP doesn't mean that other people shouldn't be protected by default.

You're knowledgeable enough to configure your DNS, you just gotta learn something different.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by zajio1am on Saturday September 07, 2019 @04:41AM (#20902590)
Not if one trusts more his/her ISP more than Cloudflare. At least, an ISP is a contractual partner and under the same jurisdiction, in Europe including GDPR.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by meowface on Saturday September 07, 2019 @03:45PM (#20906045)
For what it's worth, I trust Cloudflare an order of magnitude more than I trust my ISP (Comcast).
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by floatboth on Saturday September 07, 2019 @04:58AM (#20902650)
Being in the same jurisdiction is bad: your ISP is THE place for your local law enforcement to get info on your browsing.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by xg15 on Saturday September 07, 2019 @05:47AM (#20902811)
Yes. However with Cloudflare, now everyone would effectively be under the jurisdiction of the US which is not necessarily better.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by darkhorn on Saturday September 07, 2019 @08:45PM (#20907761)
You can change your DoH provider under the settings in Firefox.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by floatboth on Saturday September 07, 2019 @01:13PM (#20905106)
Well, it's good if you live in a non-US-friendly country :)
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by rnhmjoj on Saturday September 07, 2019 @05:14AM (#20902702)
Or if you run your own resolver and don't want a completely unrelated third party like Cloudflare siphoning your traffic.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by mtsr on Saturday September 07, 2019 @05:34AM (#20902764)
This. And I already have to deal with smart appliances that try to contact their own DNS (I’m looking at you, Samsung) and that break if I force their requests through my own resolver.

This will just allow all applications and appliances to bypass my privacy measures.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by Spivak on Saturday September 07, 2019 @01:52PM (#20905380)
I mean this is pretty much the end goal. It’s a Samsung owned, controlled, and managed device.

You as the local network operator are their adversary and it’s in Samsung’s every interest to bypass. They want and expect a clean connection to the internet. Giving it anything else is a problem to them.

If you’re installing one of these spyware devices in your network and relying on DNS to keep your information private then that’s on you when it doesn’t work. DoH neither creates nor solves human problems.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by mtsr on Thursday September 12, 2019 @06:19AM (#20949845)
I paid for the TV, why do we accept this practice?
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by ferzul on Saturday September 07, 2019 @06:18AM (#20902902)
who will write the article about the weird world we live in, where the person who is mitm'ing the network connection is me, and it's the non-mitm'ed connection that is untrusted and worrying.

at this point i expect to see talk of “the VPN”, a new network for hobbyists and academics, that's kinda like the old internet, and we only use devices that are wrapped in it.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by nathanaldensr on Saturday September 07, 2019 @07:15AM (#20903091)
I was just thinking this. It's crazy: we used to all be concerned about protecting the transport (HTTPS/TLS) but now the bigger problem seems to be the endpoints themselves being untrustworthy--"smart" appliances, Google, Facebook, Mozilla and CloudFlare with DNS-over-HTTPS. Untrustworthy endpoints using secure transport to hide malintent.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by mtsr on Saturday September 07, 2019 @06:36AM (#20902964)
Take a look at Privoxy.

It's mostly useless now with everyone defaulting to HTTPS unless you install a root certificate on all your devices.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by rnhmjoj on Saturday September 07, 2019 @11:05AM (#20904172)
This is actually what I'm doing.

With some additional duct tape[1] I made privoxy work on https too. I run an instance for each host, though it could be possible to distribute a personal CA certificate.

[1]: https://maxwell.ydns.eu/git/rnhmjoj/privoxy-tls

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by lordlimecat on Saturday September 07, 2019 @10:33AM (#20903970)
Cloudflare would also be under GDPR as it serves customers in EU.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by TheChaplain on Saturday September 07, 2019 @03:39AM (#20902391)
Well, DoH effectively bypass DNS-filters set up by countries. While some are questionable, I believe it won't take long until Mozilla ends up with some bad press, and being an underdog it doesn't need that.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by indalo on Saturday September 07, 2019 @04:22AM (#20902526)
To me that is good press, and it's something I personally would like. Seeing a state and/or adjunct corporations throwing a tantrum over this is only a measure of success.

After all privacy is the goal, isn't it?

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by zzzcpan on Saturday September 07, 2019 @06:28AM (#20902938)
> But this is a win overall for privacy.

> DNS is used by ISPs to sell user's data and is one way that oppressive regimes track what their users do.

It's not a win for privacy, ISPs will still have that data and now third parties will have that data, state actors will have that data in a nice convenient centralized locations, governments will have an ability to force those centralized providers to do censorship for them. As for oppressive regimes - they don't care about DNS data, if they want to spy on people, they will one way or another.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by lovelearning on Saturday September 07, 2019 @06:58AM (#20903036)
DoH does not imply centralization in any way. Any trusted party can provide their own DoH endpoint. I can run my own DoH server on a cheap VPS hosted in another country.

I live in an increasingly oppressive regime. Most of the blocking is done at DNS level. DoH is a great solution. Slamming DoH because they can anyway spy one way or another is a poor argument.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by tssva on Saturday September 07, 2019 @08:58AM (#20903488)
The issue is each application implementing DoH themselves. Now any software which you wish to use your own DoH resolver would have to be configured individually.

A better solution would have been for Mozilla to fund development of an enduser friendly DNS proxy application which would enable DoH system wide.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by lovelearning on Saturday September 07, 2019 @11:34AM (#20904401)
The ideal solution would be something that can be installed in any home router, but that's a non-starter because of total lack of home router configuration standards. Flashing a router is not user-friendly for anybody.

The next best solution would be your suggestion, but that too is not practical unless it comes preinstalled on all OSes because the average user won't even know they need something called a DNS proxy. I don't see OS vendors agreeing to preinstall it. Additionally, AFAIK, popular OSes like Android and iOS prior to some versions don't even allow such system-wide DNS proxy configurations.

The practical approach left then is to implement it in browsers, solving it at least for the most common use case on all devices. Everybody knows how to download and install and use browsers. In a discussion forum I frequent, average users ask for ISP censorship bypass solutions all the time. Since Chrome does not support DoH yet, among all the possible solutions - VPN, Tor, SSHproxy - using another browser is actually the most user-friendly, least expensive, most performant option. It helps that it's Mozilla's product because their trust perception is higher than Google/MS/Apple/VPN providers.

I feel Mozilla's taken a good approach overall within the scope of their area of expertise.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by zzzcpan on Saturday September 07, 2019 @12:07PM (#20904643)
DNS-based censorship doesn't work well enough for governments to be useful, it's always just a first step towards much more aggressive censorship tech. You should not advice people to use DoH to circumvent censorship, Tor is a decent longer term solution, and so are private VPNs, proxies.

Although I find it suspicious that there is just DNS filtering on your ISPs side and no IP filtering. Is it at the stage where it's not even enforced, semi-voluntary censorship by ISPs? Otherwise once the government starts checking compliance it will force IP-based filtering too, where DNS filtering circumvention is useless. And governments don't care about how broad the filtering is. Russia, for example, blocked half of the internet once in an attempt to censor Telegram.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by lovelearning on Saturday September 07, 2019 @12:37PM (#20904845)
It is semi-voluntary and I don't think it's enforced for now - not heard of any end user getting punished by government for circumventing.

DoH is a simple solution that works for now. TorBrowser takes it to the other extreme - it's a good secure solution (I think), but not required as of now, and seen as slow with plugin and other usage restrictions. VPNs, proxies are not seen as good solutions because people prefer free to paid, and they are not as trusted as CF and Mozilla. Self-managed VPNs/proxies are not easy for the average person to setup.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by jedisct1 on Saturday September 07, 2019 @11:53AM (#20904543)
Meanwhile, dnscrypt-proxy, that has been doing exactly that since 2011, is still looking for help with developing MacOS and Android user interfaces.