Dave explains the Crowdstrike IT outage, focusing in on its role as a kernel mode driver. For my book on the spectrum, see: https://amzn.to/3XLJ8kYFollow me...
  • Winged_Hussar@lemmy.worldEnglish
    29·
    4 months ago

    Very interesting, especially how they’re executing unsigned code via the *.sys files to (presumably) get around waiting for MS to re-sign their driver.

    • wolfylow@lemmy.worldEnglish
      21·
      4 months ago

      Yeah this was the main take-away for me, too. You’d expect they’d have ironclad QA when doing shit like this.

  • magic_lobster_party@kbin.run
    25·
    4 months ago

    I like when videos are as direct as this guy’s. Just straight to the point. No extra fluff, distracting skits or drama. It’s just him talking straight to the camera about things he’s passionate about.

  • peopleproblems@lemmy.worldEnglish
    22·
    4 months ago

    That answered a lot of questions.

    I hope they publicly state how they pushed a bad file, but I doubt it.

    Seems like someone really didn’t pay attention to what they were doing, and they might have an internal problem with QA.

    • andrew_bidlaw@sh.itjust.worksEnglish
      16·
      4 months ago

      they might have an internal problem with QA.

      They don’t have a lack of quality assurance. They have a lack-of-quality assurance.

      • sunzu@kbin.run
        71·
        4 months ago

        This likely going to be text book case of how to not a run a company in a dominant market position that caused world wide system failures.

        Makes you wonder if we should be allowing such consolidtion in critical industries. This ain’t even about economics anymore. More of a infrastructure and national security decision.

        Or fucking supervivise and train people properly… I don’t know. Sounds like management problems.

    • SauceFlexr@lemmy.worldEnglish
      13·
      4 months ago

      As someone that works in QA, yeah, they needed something to catch this. I saw someone mention somewhere without a source that they missed it as all test machines have their full suite of software installed. In that scenario, the computer wasn’t affected. So for QA it seems their labs might need to be more in tune with the user base.

      However, the fact that they are able to push this so quickly worldwide seems like a big process issue. I get 0 day issues and that is how they justify it. But deploy to a small subset of customers before going global seems more reasonable.

      • NateSwift@lemmy.dbzer0.comEnglish
        9·
        4 months ago

        I heard somewhere that the updated ignored staging settings set. So even if companies had it set to only roll out to a subset of their computers it went everywhere

        • SauceFlexr@lemmy.worldEnglish
          5·
          4 months ago

          Oof. Then that seems more on the ops side of things. Interesting. I can’t wait for them to never share what happened so we can all continue to speculate. 😂

      • 0x0@programming.devEnglish
        3·
        4 months ago

        I read somewhere (commentes in that video) that CS ignored their own customer-configured stagger upgrades for some upgrades…

        • dan@upvote.auEnglish
          4·
          4 months ago

          Apparently those settings are only for updates to the software itself, not for updates to the definition files.