News for hackers. Stuff that matters.
Re:Shutting down our unencrypted public DNS service by adgjlsfhk1 on Tuesday December 13, 2022 @10:45AM (#33970336)
it is privacy. The ISP and routers can see the IP addresses but that gives a lot less info than the url since most websites will pull from a changing set of IPs due to server changes, cdns, and 3rd party content (e.g. ads). For a large number of sites, the IP addresses will just tell you that someone is looking at a website hosted by cloudflare/aws.

(also just getting rid of the name is effective at getting the info away from low tech surveillance like schools where someone on the route is mildly interested in seeing/blocking connections but won't bother if it's annoying to do)

Re:Shutting down our unencrypted public DNS service by PaulHoule on Tuesday December 13, 2022 @10:55AM (#33970531)
There are many content blocking solutions that work at the DNS level. Encrypted DNS will bypass those.
Re:Shutting down our unencrypted public DNS service by Avamander on Tuesday December 13, 2022 @11:40AM (#33971293)
Only if you don't control the device, in which case you're dead in the water anyways.
Re:Shutting down our unencrypted public DNS service by PaulHoule on Tuesday December 13, 2022 @11:59AM (#33971659)
I am thinking about the system they use to censor the WiFi at the gym which works at the network level.
Re:Shutting down our unencrypted public DNS service by quickthrower2 on Tuesday December 13, 2022 @04:13PM (#33975877)
Gym… and China
Re:Shutting down our unencrypted public DNS service by hedora on Tuesday December 13, 2022 @12:56PM (#33972847)
Doesn't the TLS / HTTPS handshake still send the destination host name in cleartext?
Re:Shutting down our unencrypted public DNS service by adgjlsfhk1 on Tuesday December 13, 2022 @04:20PM (#33975983)
https://www.ibm.com/docs/en/sdk-java-technology/8?topic=hand... doesn't look like it (at least with tls 1.3)