• peopleproblems@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    2 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.works
      cake
      link
      fedilink
      English
      arrow-up
      9
      ·
      2 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.

    • SauceFlexr@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 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.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 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.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 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. 😂

  • Winged_Hussar@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    2 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.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      2 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.