News for hackers. Stuff that matters.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by nojs on Wednesday July 16, 2025 @02:57AM (#44579477)
Who? Honest question
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Elucalidavah on Wednesday July 16, 2025 @03:45AM (#44579723)
Realistically, either you ignore the privacy concerns and set up routing to multiple providers preferring the fastest, or you go all-in on privacy and route DNS over Tor over bridge.

Although, perhaps, having an external VPS with a dns proxy could be a good middle ground?

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Tijdreiziger on Wednesday July 16, 2025 @06:47AM (#44580747)
Middle ground is ISP DNS, right?
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by davidcbc on Wednesday July 16, 2025 @06:23PM (#44587462)
If privacy is your primary concern I would 100% trust Cloudflare or Google over an ISP in the US
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Tijdreiziger on Thursday July 17, 2025 @04:57AM (#44591210)
I’m in the Netherlands.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by daneel_w on Wednesday July 16, 2025 @08:36AM (#44581585)
If you're the technical type you can run Unbound locally (even on Windows) and let it forward queries with DoT. No need for neither Tor nor running your own external resolver.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by misiek08 on Wednesday July 16, 2025 @03:42AM (#44579705)
Google is serving you ads, CF isn’t.

And it’s not conspiracy theory - it was very suspicious when we did some testing on small, aware group. The traffic didn’t look like being handled anonymously at Google side

Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by mnordhoff on Wednesday July 16, 2025 @03:47AM (#44579730)
Unless the privacy policy changed recently, Google shouldn't be doing anything nefarious with 8.8.8.8 DNS queries.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by DarkCrusader2 on Wednesday July 16, 2025 @04:19AM (#44579912)
They weren't supposed to do anything with our gmail data as well. That didn't stop them.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Tijdreiziger on Wednesday July 16, 2025 @06:48AM (#44580752)
[citation needed]
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by johnklos on Wednesday July 16, 2025 @10:16AM (#44582651)
Read their TOS.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by Tijdreiziger on Wednesday July 16, 2025 @03:42PM (#44586041)
If it’s in the ToS, then it’s not true that “[they] weren't supposed to do anything with our gmail data”.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by daneel_w on Wednesday July 16, 2025 @09:24AM (#44582075)
Yeah it's not like they have a long track record of being caught red-handed stepping all over privacy regulations and snarfing up user activity data across their entire range of free products...
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by opan on Wednesday July 16, 2025 @12:54PM (#44584436)
CF breaks half the web with their awful challenges that fail in many non-mainstream browsers (even ones based on chromium).
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by immibis on Wednesday July 16, 2025 @07:06AM (#44580862)
Myself, I suppose? Recursive resolvers are low-maintenance, and you get less exposure to ISP censorship (which "developed" countries also do).
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025 by daneel_w on Wednesday July 16, 2025 @08:34AM (#44581567)
Quad9, dns0.