this post was submitted on 22 Jul 2024
586 points (97.6% liked)

Technology

59428 readers
2858 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
586
CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed (www.neowin.net)
submitted 3 months ago by hal_5700X@sh.itjust.works to c/technology@lemmy.world
83 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] b161@lemmy.blahaj.zone 2 points 3 months ago (2 children)

Do you know if the sensor update policy had been set to N-2 would this have avoided the issue?

[–] starneld@infosec.pub 7 points 3 months ago (1 children)

Setting the update policy to N-2 (or any other configuration) would not have avoided the issue. The Falcon sensor itself wasn’t updated, which is what the update policy controls. As it turns out, you cannot control the content channel updates - you simply always get the updates.

[–] b161@lemmy.blahaj.zone -1 points 3 months ago

💀 Fucking hell CrowdStrike.

[–] quinkin@lemmy.world 2 points 3 months ago

No it would not.