News for hackers. Stuff that matters.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by tannhaeuser on Saturday September 07, 2019 @05:23AM (#20902733)
Same story as always with Google "innovations": "hey, we're preventing DNS queries to go to your ISP who is selling it" (to go to our service instead so we can profit from it).

It's scary that Moz sides with monopolies like Google and Cloudflare on this one.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by LUmBULtERA on Saturday September 07, 2019 @08:38AM (#20903396)
In my Firefox settings I can choose any DoH provider I want, not just Cloudflare. Naturally something has to be set up as a default so it works. Why is adding DoH in the browser a bad thing?
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by josteink on Saturday September 07, 2019 @12:19PM (#20904718)
Because if we’re replacing classic DNS with something new, it needs to be part of the OS.

Not reimplemented (and configured) per application. The user and OS should control the application, not the other way around.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by Faark on Saturday September 07, 2019 @03:22PM (#20905909)
Is any OS vendor working on something like that? Or do you expect Moz to jump into OS dev as well? I'd expect them to import settings from OS as soon as a major OS provides this for DoH.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by tannhaeuser on Saturday September 07, 2019 @03:50PM (#20906075)
The DNS has grown into a regulated service, with TLD authorities and protocols to follow for registrators, transparency for domain holders, many registrators to choose, etc. Do you want to replace it by a centralized system run by very few monopolies that track resolution queries by IP?
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by jedisct1 on Saturday September 07, 2019 @12:06PM (#20904629)
At the end, you still need to trust the resolver.

There is a proposal to improve this. Resolves won't know client IPs any more: https://github.com/DNSCrypt/dnscrypt-protocol/blob/master/AN...

Reference client and server implementations should be ready in the next few days.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by vavrusa on Saturday September 07, 2019 @02:22PM (#20905569)
This is interesting as a lighter alternative to DNS over Tor. Where is the padding going to be? Basic clients won't add EDNS padding by default, but intuitively there has to be padding somewhere. It reminds me of https://odns.cs.princeton.edu (I haven't seen a working implementation of that one yet). The most difficult challenge is how to present the ultimate choice - use the relay and maybe get slower Internet, or don't use the relay and maybe get tracked. What hasn't been much explored yet is using resolvers just to obtain the delegation (nobody needs to know who the client is for that), but that itself is not without problems.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by jedisct1 on Saturday September 07, 2019 @04:59PM (#20906475)
Indeed, we will need to make a choice between minimizing latency or using a relay.

But a lot of people use DNS over Tor already. For people concerned about privacy, a bit of extra latency is totally acceptable.

Anonymized DNSCrypt is lighter than Tor, has a very clear security model, and relays are less vulnerable to abuse than Tor exit nodes.

The server/relay part is going to be implemented in https://github.com/jedisct1/rust-dnscrypt-server

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by jedisct1 on Saturday September 07, 2019 @04:47PM (#20906419)
The underlying DNSCrypt protocol does the padding already: https://dnscrypt.info/protocol

DNS queries and responses are wrapped, they are never modified. EDNS padding is a horrible hack.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by vavrusa on Saturday September 07, 2019 @05:05PM (#20906505)
That's good, I missed that. Thanks for highlighting the project, I'll keep an eye on it!