3 ms·
Playing Devil's advocate: when you run your site on any provider, except maybe colo'ing, you're also giving them access to that data, as they could peek into th
by icebraining 9y ago
Playing Devil's advocate: when you run your site on any provider, except maybe colo'ing, you're also giving them access to that data, as they could peek into the system's memory . Using Cloudflare is just adding a second provider.
- LethargicStud 9y agoSure, but Google or AWS looking at your specific certs and using them to decrypt your traffic or impersonate you is probably far less likely than someone MITMing Cloudflare's connection to your server or even worse finding a vulnerability in CF (see cloudbleed [1]). I really really dislike how Cloudflare has legitimized MITMing many sites while making it look 'secure'. It's basic security, never trust someone else with your keys. 1: https://en.m.wikipedia.org/wiki/Cloudbleed https://en.m.wikipedia.org/wiki/Cloudbleed
- pilsetnieks 9y ago> Using Cloudflare is just adding a second provider. Thus immediately increasing risk by 100%. In actuality though, even more - if you use the setup where the connection between you and CF is not encrypted. In that case any hop along the way between you and CF could intercept the data.