• @[email protected]
    link
    fedilink
    English
    84 months ago

    Serious question, can you not? There isn’t an option to…like…set a review system first?

    • Encrypt-Keeper
      link
      English
      164 months ago

      For antivirus definitions? No, and you wouldn’t want to.

          • @wolfylow
            link
            English
            224 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.

          • @[email protected]
            link
            fedilink
            English
            24 months ago

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

            • @[email protected]
              link
              fedilink
              English
              74 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.

            • @quinkin
              link
              English
              24 months ago

              No it would not.