this post was submitted on 19 Jul 2024
56 points (98.3% liked)

chapotraphouse

13541 readers
765 users here now

Banned? DM Wmill to appeal.

No anti-nautilism posts. See: Eco-fascism Primer

Gossip posts go in c/gossip. Don't post low-hanging fruit here after it gets removed from c/gossip

founded 3 years ago
MODERATORS
LENINSGHOSTFACEKILLA@hexbear.net
MiraculousMM@hexbear.net
KenBonesWildRide@hexbear.net
Nakoichi@hexbear.net
itsPina@hexbear.net
corgiwithalaptop@hexbear.net
PorkrollPosadist@hexbear.net
ZoomeristLeninist@hexbear.net
EmmaGoldman@hexbear.net
InsidiousTrackers@hexbear.net
sweet_pecan@hexbear.net
a_little_red_rat@hexbear.net
56
A security engineer's short ELI5 thread on what seems to be the cause of the CrowdStrike outage. (subium.com)
submitted 4 months ago by InevitableSwing@hexbear.net to c/chapotraphouse@hexbear.net
22 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Chronicon@hexbear.net 7 points 4 months ago

No, they actually just pushed out a bugged driver that they use to hook into the windows kernel. Turned out to be nothing to do with the realtime A/V feed. Which is honestly funnier because there is NO reason to push that type of update out worldwide in one go, it should be done in stages to catch bugs like this before they go global...

The OP thread talked about it just below the "Load More Replies" fold