Tell HN: Camelgate NPM Outage (Cloudflare) EDIT: Back online?! NPM discussion: https://github.com/npm/cli/issues/8203 NPM incident: https://status.npmjs.org/incidents/hdtkrsqp134s Cloudflare messaging: https://www.cloudflarestatus.com/incidents/gshczn1wxh74 GitHub issue: https://github.com/sindresorhus/camelcase/issues/114 Anyone experiencing npm outage that's more than just the referenced camelcase package? |
That rule can be overridden if you're having this issue on your own site.
What engineer at cloudflare thought this was a good resolution?
Some discussion here https://github.com/npm/cli/issues/8203
Edit: this is resolved now https://status.npmjs.org/incidents/hdtkrsqp134s
Cementing its track record as a product that mostly doesn't do anything except for occasionally break the internet here and there to keep things fun and interesting.
I wouldn't say that. The postmortem you referred to links to another CloudFlare blog post - one about a pretty serious RCE vuln in Microsoft SharePoint that was blocked by their WAF: https://blog.cloudflare.com/stopping-cve-2019-0604/
I would have thought a large company like GitHub or Microsoft can have their own WAF team for their apps.
(NPM is owned by GitHub, and GitHub is owned by Microsoft)
Honestly what I'd _love_ to see is AWS, GCE, Azure, Fastly, Cloudflare and Akamai band together and share information about such bad actors, compile evidence lists and file abuse reports against their ISP - or in case the ISP is a "bulletproof hoster" or certain enemy states, initiate enforcement actors like governments to get these bad ISPs disconnected from the Internet.