News for hackers. Stuff that matters.
Re:DNS over HTTPS by bandrami on Wednesday January 17, 2018 @06:47AM (#16167155)
Actual DNS servers and clients have supported TLS since the early years of this decade. What's gained by adding HTTP transport overhead?
Re:DNS over HTTPS by est on Wednesday January 17, 2018 @06:59AM (#16167213)
http is not overhead, http is the only transport that can go through middle boxes.
Re:DNS over HTTPS by skuzye on Wednesday January 17, 2018 @07:36AM (#16167371)
if the traffic is encrypted how can you tell whether it's http or plain dns?
Re:DNS over HTTPS by jedisct1 on Sunday January 21, 2018 @03:54PM (#16199972)
Because the purpose of middle boxes is to log your traffic no matter what, usually by installing a root certificate on your devices.
Re:DNS over HTTPS by throwaway2048 on Wednesday January 17, 2018 @07:26AM (#16167324)
What dns servers and clients support TLS?
Re:DNS over HTTPS by bandrami on Wednesday January 17, 2018 @07:32AM (#16167346)
Unbound does it natively, and BIND and the rest use DNSCrypt's shim
Re:DNS over HTTPS by LogicX on Wednesday January 17, 2018 @08:34AM (#16167720)
While we at DNSFilter are working on support of DNSCrypt, just to add some flavor to your note... it should be mentioned that the original author just abandoned the project, removed the repos from his github user, shut down the website, and it's been setup by a few industry players under a new github org: https://github.com/DNSCrypt

Tough to say what direction the project will take.

I for one welcome other advancements such as Google's efforts.

FWIW, my understanding is if you use Chrome it actually communicates over QUIC