3 ms·

Can you elaborate on these extra internal controls?

• jeffbee 6y ago
  Google is pretty vocal about how only reviewed, submitted, and hermetically built code can run in production, how they audit such things, how their hardware security module helps them achieve this, etc. Cloudflare has been pretty vocal about the opposite: how they use tons of off-the-shelf software components, vendor firmware, etc. There's no reason to believe that Cloudflare is as able to provide the privacy they promise as Google is.
  • dundarious 6y ago
    Caveat that I am a DNS layman, but I disagree that Google's logging described in https://developers.google.com/speed/public-dns/privacy https://developers.google.com/speed/public-dns/privacy is equivalent to Cloudflare's described in https://developers.cloudflare.com/1.1.1.1/privacy/public-dns-resolver/ https://developers.cloudflare.com/1.1.1.1/privacy/public-dns... Google keeps Permanent Logs and doesn't make it easy for me to see whether that information can be shared and to whom. Cloudflare only stores Public Resolver Logs, deletes them after 25 hours, and acknowledges it shares an anonymized subset of the data only with APNIC Labs. Your comments about build pipeline and firmware are interesting, and to me fall into two rough camps: * preventing bugs from leaking private info: to be honest, I trust neither on this, and I'm more worried about Google being sneaky in its ToS than Cloudflare being sloppy in their dev process. * preventing infiltration from state actors and hackers -- this is a non-goal for me. So for my goal of limiting the power of surveillance capitalism on my life, Cloudflare appears to be a clear winner.