←back to thread

120 points bavarianbob | 1 comments | | HN request time: 0.267s | source

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?

Show context
pvg ◴[] No.43550246[source]

This is not CF WAF's first rodeo >>20421538 →

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.

replies(3): >>43550290 #>>43550388 #>>43552686 #
lynnesbian ◴[] No.43552686[source]

> a product that mostly doesn't do anything except for occasionally break the internet

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/

replies(1): >>43553386 #
pvg ◴[] No.43553386[source]

I mean, it's hardly surprising CloudFlare will tell you this is a useful product. But it is to securing a web application what regex is to parsing HTML.

replies(1): >>43554621 #
1. jiggawatts ◴[] No.43554621[source]

Sadly I work with web developers that all assume they don’t need to bother too much with security “because we have a WAF”.