• skuzz@discuss.tchncs.de
    link
    fedilink
    arrow-up
    8
    ·
    4 months ago

    Not even that. Kernel drivers are supposed to be Microsoft WHQL certified through a thorough testing process (that would have caught it in 3 minutes) before Microsoft will cryptographically sign them.

    …but apparently Microsoft allows AV vendors to skip WHQL certification testing.

    • flambonkscious@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 months ago

      …sorta. The complexity here is their driver is signed, but it’s also loading code from their channel file (that was all zeroed out), and it seems the necessary error checking wasn’t implemented.

      I haven’t yet got to the root cause they published, this is just what I gathered from the video of a retired MS kernel dev who posts stuff.

      Obviously with their design it allowed them to be flexible at the cost of playing with fire - I’m impressed they got away with it for so long, really