News for hackers. Stuff that matters.
Re:Mozilla’s DNS over HTTPs by djsumdog on Tuesday February 25, 2020 @01:16PM (#22415609)
American ISPs can and do sell your data legally. I don't really trust my ISP (I run my own DNS server at home and tunnel its requests over to a cloud VM), but I trust Cloudflare even less.
Re:Mozilla’s DNS over HTTPs by 9HZZRfNlpR on Tuesday February 25, 2020 @05:12PM (#22418038)
I trust my ISP but not American companies. They roll out only in America but obviously it's coming, and they use locale to detect it? My locale is set to en_US too, surely I'm not alone doing it because of translated software. Firefox has a small market in America anyway and America is not the world. We know big tech is in bed with your three letter agencies.
Re:Mozilla’s DNS over HTTPs by nullc on Tuesday February 25, 2020 @03:23PM (#22417040)
"Legally" is dubious. Intercepting any private wire communication is a clear violation of federal law (e.g. 18 U.S. Code § 2511), and a violation of the law in many states (e.g. CA PC 631).

Unfortunately, the US government is one of the larger users of ISP surveillance activities, benefiting through the purchase of private data as well as using administrative subpoena to obtain the data collected by ISPs without due process or meaningful oversight.

This creates a conflict of interest which I believe is preventing the US from zealously enforcing existing criminal law which would be otherwise sufficient to significantly reduce surveillance by communications providers.

Re:Mozilla’s DNS over HTTPs by djsumdog on Tuesday February 25, 2020 @03:47PM (#22417244)
Are you sure about that? This passed in 2017 and I don't think it's been reversed:

http://clerk.house.gov/evs/2017/roll202.xml

Re:Mozilla’s DNS over HTTPs by nullc on Tuesday February 25, 2020 @08:59PM (#22419597)
Hm. FCC getting a ruling overturned that strengthens the law doesn't change the existing law, however.
Re:Mozilla’s DNS over HTTPs by saagarjha on Wednesday February 26, 2020 @03:32AM (#22421400)
Wow, that's one polarized vote…
Re:Mozilla’s DNS over HTTPs by syshum on Tuesday February 25, 2020 @02:10PM (#22416202)
I dont use my ISP as my DNS provider, I have a custom setup using PiHole and other methods to provide secure DNS Resolution

Firefox should not be forcing this shit on me, time to search for yet another browser that will respect users. Mozilla is clearly more interested in commercial viability via their partnerships with large corporations (like CloudFlare) then in protecting Users

Re:Mozilla’s DNS over HTTPs by zamalek on Tuesday February 25, 2020 @03:01PM (#22416798)
The only way to solve the ISP DNS inspection problem is by one of:

* Using DoH. For this to work with PiHole, you need to have a DoH resolver on the device, and then instruct the PiHole to recurse to that resolver instead - possibly your own in a VM somewhere?

* Using a permanent encrypted VPN to your own machine in the cloud and routing all DNS through that, then recursing to some DNS that you trust.

* Write your own encrypted protocol that communicates with some machine in the cloud.

Anything else and your ISP/evil-state-actor is able to to see your DNS traffic in plain-text. PiHole and DoH approach the problem at different OSI layers, you ideally need both.

Re:Mozilla’s DNS over HTTPs by syshum on Wednesday February 26, 2020 @03:52AM (#22421474)
>>Anything else and your ISP/evil-state-actor is able to to see your DNS traffic in plain-text

and you believe CloudFlare is not a "evil state actor" or has not been compromised or never will be compromised by an "evil state actor"

Wow your faith in CloudFlare is much much higher than mine

Personally I trust my current ISP (which is not one of the big boys) more than I trust CloudFlare.

I do not trust cloudflare at all and believe they are the are one of the biggest threats to the future of open web there is today.

Re:Mozilla’s DNS over HTTPs by zamalek on Wednesday February 26, 2020 @05:54PM (#22428355)
Cloudflare aren't the only people running a DoH endpoint
Re:Mozilla’s DNS over HTTPs by alwillis on Tuesday February 25, 2020 @05:21PM (#22418132)
DNS over TSL (DoT) is a much better alternative to DoH, at least when it comes to the ability to be tracked.

For example, because it’s not using HTTP, there are no cookies or SNI to worry about.

More at https://news.ycombinator.com/item?id=22418005.

Re:Mozilla’s DNS over HTTPs by growse on Tuesday February 25, 2020 @06:27PM (#22418675)
> DNS over TSL (DoT) is a much better alternative to DoH, at least when it comes to the ability to be tracked.

> For example, because it’s not using HTTP, there are no cookies or SNI to worry about.

> More at https://news.ycombinator.com/item?id=22418005.

The fact that it can be trivially blocked by anyone on the network path does not make it "much better".

Re:Mozilla’s DNS over HTTPs by alwillis on Tuesday February 25, 2020 @09:46PM (#22419816)
The fact that it can be trivially blocked by anyone on the network path does not make it "much better".

Of course anyone on the "network path" can block almost any protocol; DoT isn’t unique in that regard.

The concern is many large businesses block port 853 but that's because prior to the development of DoT, there was no reason for IT departments to configure firewalls to enable it. Most organizations only have a handful of ports available, including 443, which is what HTTPS uses and therefore DoH works as a result.

I've been running DNS over TLS using the Unbound [1] resolver for my home LAN on a spare laptop for a few weeks now and it’s been great.

Given the privacy trade-offs between privacy and security, many IT departments would opt to make port 853 available for DoT rather than increasing the ability for their users to be tracked.

As I mentioned elsewhere in this thread, the article Centralised DoH is bad for Privacy, in 2019 and beyond [2] clearly describes the issues with DoH:

DNS over HTTPS opens up DNS to all the tracking possibilities present in HTTPS and TLS. As it stands, DNS over UDP almost always gets some free privacy by mixing all devices on a network together – an outside snooper sees a stream of queries coming from a household, a coffeeshop or even an entire office building, with no way to tie a query to any specific device or user. Such mixing of queries provides an imperfect but useful modicum of privacy.

DNS over HTTPS however neatly separates out each device (and even each individual application on that device) to a separate query stream. This alone is worrying, as we now have individual users’ queries, but the TLS that underlies HTTPS also typically uses TLS Resumption which offers even further tracking capabilities.

[1]: https://www.ctrl.blog/entry/unbound-tls-forwarding.html

[2]: https://labs.ripe.net/Members/bert_hubert/centralised-doh-is...

Re:Mozilla’s DNS over HTTPs by zamalek on Tuesday February 25, 2020 @07:02PM (#22418900)
DoT only solves the SNI problem during the DNS request itself. It doesn't do a thing about the SNI during the request to the actual website, which is where all the privacy concerns are.
Re:Mozilla’s DNS over HTTPs by alwillis on Tuesday February 25, 2020 @10:08PM (#22419921)
DoT only solves the SNI problem during the DNS request itself. It doesn't do a thing about the SNI during the request to the actual website, which is where all the privacy concerns are.

Sure, but until we have encrypted SNI, which is in draft, meta data is going to leak, but that's a separate issue from either DoT or DoH.

But because DoT doesn't use HTTPS, you don't get some of its downsides like using cookies for tracking, for example.

Re:Mozilla’s DNS over HTTPs by zamalek on Wednesday February 26, 2020 @12:00AM (#22420409)
DoH (edit from DoT) doesn't use cookies, it is stateless. But your original comment didn't mention that anyway, it only mentioned SNI.
Re:Mozilla’s DNS over HTTPs by alwillis on Wednesday February 26, 2020 @01:58AM (#22420964)
From "The Big DNS Privacy Debate" [1]:

DoH shares the benefits and downsides of HTTPS. It sends out more trackable data than regular DNS, simply because HTTP supports things like headers and cookies. TLS session resumption functions as another tracking mechanism.

There’s a draft RFC [2] to address these and other privacy issues that weren't specified in the original RFC for DoH.

[1]: https://labs.ripe.net/Members/bert_hubert/the-big-dns-privac...

[2]: https://www.ietf.org/archive/id/draft-dickinson-doh-dohpe-00...