News for hackers. Stuff that matters.
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