1.1.1.1: Fast, privacy-first consumer DNS service

Re:1.1.1.1: Fast, privacy-first consumer DNS service by tyingq on Sunday April 01, 2018 @12:08PM (#16728981)

Sorry, confused. Https requests are prolific, while encrypted DNS requests aren't. Why isn't the former less hard to detect?

[ Parent | on HN ]

Re:1.1.1.1: Fast, privacy-first consumer DNS service by ori_b on Sunday April 01, 2018 @03:36PM (#16730007)

How would you tell that an encrypted chunk of data is HTTPS instead of DNS? The best you'd be able to do is guess based on behavior that it's DNS.

[ Parent | on HN ]

Re:1.1.1.1: Fast, privacy-first consumer DNS service by tyingq on Monday April 02, 2018 @08:10PM (#16740681)

Destination port might be easy to differentiate dns over tls vs dns over https :)

[ Parent | on HN ]

Re:1.1.1.1: Fast, privacy-first consumer DNS service by forapurpose on Sunday April 01, 2018 @02:53PM (#16729817)

Perhaps if the attacker filters traffic first by protocol, it's harder but not at all impossible. I'd guess that DNS-over-HTTPS packets won't be hard to identify by other means.

[ Parent | on HN ]

Re:1.1.1.1: Fast, privacy-first consumer DNS service by patrickmcmanus on Sunday April 01, 2018 @03:12PM (#16729898)

of course dns over https to cloudflare can be mixed on the same h2 connection with other https to the same host. It starts to get interesting.

(this is one of the advantages of https vs straight tls)

[ Parent | on HN ]