It doesn't matter, the CEO will be just fineI'm wondering how CrowdStrike as a company fares from this issue? Stock is currently down 10%
Yes the formatting breaks on mobile tooThe file is C-00000291*.sys, not C0000.... the article is missing the "-".
I dunno, they seem to be living up to their name here already; they struck the crowd, alright, open-handed right across the boot process.Time for them to rebrand as CloudStrike?
I'm confused how seeing their name in the stack trace means that the rest of that story has to be true ...
I don't think it's a formatting issue, as the dash in the filename is missing on desktop as well, and as far as I can tell, also in the source.Yes the formatting breaks on mobile too
This is why you never deploy on Fridays.Microsoft recommends restoring your systems using a backup from before 4:09 UTC on July 18 (just after midnight on Friday, Eastern time)
Agile ≠ no QA. CrowdStrike's is just a shitty development process it seems.Move fast and break things! Got to be agile!
AV software works the same way as viruses do. It kinda has to.Why the fuck does this thing need a bloody kernel driver??
Surely it's "YOUR production"?
I suspect their customers and rival vendors might already refer to it as being Crowdstruck.Time for them to rebrand as CloudStrike?
Because if it doesn't, it sucks at being AV software.Why the fuck does this thing need a bloody kernel driver??
When it's Thursday in the USA it's Friday in Australia and Japan. The answer isn't to not deploy, it's thorough testing and a progressive rollout.This is why you never deploy on Fridays.
They'll be fine; SolarWinds is still around, after all.I'm wondering how CrowdStrike as a company fares from this issue? Stock is currently down 10%
Indeed. I've been burned in many much more minor ways by updates and am now extremely reluctant to install any. That's probably too conservative, but where is the sane middle ground??This underscores what a terrifying responsibility it is to push out updates.
Microsoft's Azure status page outlines several fixes. The first and easiest is simply to try to reboot affected machines over and over, which gives affected machines multiple chances to try to grab CrowdStrike's non-broken update before the bad driver can cause the BSOD. Microsoft says that some of its customers have had to reboot their systems as many as 15 times to pull down the update.
It's hard to top this one, lol.Have you tried turning it off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on and off and on again?
"We understand the gravity of the situation and are deeply sorry for the inconvenience and disruption," wroteCrowdStrike CEO George Kurtz
It really feels like even just… a moderately passable attempt at best practices with update deployments could avoid all of this? There’s no way all these major enterprises are installing software that can just update itself without telling anybody, right?
Which would mean that somebody, somewhere at most of these companies pushed play on the update without installing it on so much is a single test box first?
Either that, or it was more of a Trojan thing where the issue didn’t start popping up for a while after the update?