3 ms·
Okay, so i have multiple problems with this blog post. I want to give the author the benefit of the doubt. They're a CTO at some startup, surely they know how c
by scrollaway 5y ago
Okay, so i have multiple problems with this blog post. I want to give the author the benefit of the doubt. They're a CTO at some startup, surely they know how cloudflare works. But i dug a bit and i don't see evidence of this.
In short, for the non-cloudflare-users among the HN crowd, and since this is a super clickbaity title, cloudflare is a reverse proxy. ALL IPs in the user's access.log, unless explicitly configured otherwise, will be cloudflare's.
Cloudflare also doesn't proactively update its cache. It does so on demand.
What I'm really confused with is if they did indeed talk to CF support, how was this not caught by the support agents? Could they genuinely be CF IPs? Having a hard time believing that.
Anyway, first step would be to look at the x-forwarded-for header. If not available, since these are logs, cloudflare has traffic analytics and wouldn't confuse its own IPs in the mix.
- ceejayoz 5y agoTheir previous detailing of GoDaddy/Microsoft issues has the same sort of "it's someone else's fault!" but reads heavily like a misunderstanding on the poster's part. https://kmitov.com/posts/godaddymicrosoft-365-and-how-an-email-was-compromised-for-about-a-day/ https://kmitov.com/posts/godaddymicrosoft-365-and-how-an-ema... (In this case, that GoDaddy resells Office 365, and the interactions between the two.)