Lemmy - RazBot
  • Communities
  • Create Post
  • Create Community
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
Hal-5700X@sh.itjust.works to Technology@lemmy.worldEnglish · 10 months ago

CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed

www.neowin.net

external-link
message-square
80
fedilink
586
external-link

CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed

www.neowin.net

Hal-5700X@sh.itjust.works to Technology@lemmy.worldEnglish · 10 months ago
message-square
80
fedilink
CrowdStrike recently caused a widespread Blue Screen of Death (BSOD) issue on Windows PCs, disrupting various sectors. However, this was not an isolated incident, CrowdStrike affected Linux PCs also.
  • AlecSadler@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    10 months ago

    But it sounds like this added files / drivers or something, not just antivirus rules?

    • 𝓢𝓮𝓮𝓙𝓪𝔂𝓔𝓶𝓶@lemmy.procrastinati.org
      link
      fedilink
      English
      arrow-up
      26
      ·
      10 months ago

      Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)

      • wolfylow@lemmy.world
        link
        fedilink
        English
        arrow-up
        22
        ·
        10 months ago

        Found this post that explains what happened in detail: https://lemmy.ohaa.xyz/post/3522666

        As an application developer (rather than someone who can/does code operating systems) I was just left open-mouthed …

        Looks like they’re delivering “code as content” to get around the rigour of getting an updated driver authorised by MS. I realise they can’t wait too long for driver approval for antivirus releases but surely - surely - you have an ironclad QA process if you’re playing with fire like this.

      • AlecSadler@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        10 months ago

        Oh, wow.

      • b161@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 months ago

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

        • starneld@infosec.pub
          link
          fedilink
          English
          arrow-up
          7
          ·
          10 months ago

          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
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            2
            ·
            10 months ago

            💀 Fucking hell CrowdStrike.

        • quinkin@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          10 months ago

          No it would not.

    • mox@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 months ago

      https://nitter.poast.org/patrickwardle/status/1814343502886477857

Technology@lemmy.world

technology@lemmy.world

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]

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


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


  • @[email protected]
  • @[email protected]
  • @[email protected]
  • @[email protected]
Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 2.87K users / day
  • 9.55K users / week
  • 18.1K users / month
  • 37.6K users / 6 months
  • 1 local subscriber
  • 69.9K subscribers
  • 13.6K Posts
  • 567K Comments
  • Modlog
  • mods:
  • L3s@lemmy.world
  • enu@lemmy.world
  • Technopagan@lemmy.world
  • L4sBot@lemmy.world
  • L3s@hackingne.ws
  • L4s@hackingne.ws
  • BE: 0.19.9
  • Modlog
  • Legal
  • Instances
  • Docs
  • Code
  • join-lemmy.org