Microsoft wants to avoid another CrowdStrike incident.
    • doc@fedia.io
      60·
      24 days ago

      Another big area of Windows that uses kernel-level drivers is anti-cheating engines for games. Microsoft has been speaking with game developers about how to reduce the amount of kernel usage, but it’s a more complicated use case as cheaters often have to purposefully tamper with their machine to disable protections and get cheating engines running.

      “A lot of [game developers] would love to not have to maintain kernel stuff, and they are very interested in how they do that,” Weston says. “We’ve been talking about the requirements there, and I think we’ll have more to say on that in the near future.” Riot Games told me last year that it’s willing to follow potential Windows security changes and “recede from the kernel space.”

      • kubica@fedia.io
        43·
        24 days ago

        “A lot of [game developers] would love to not have to maintain kernel stuff, and they are very interested in how they do that,”

        I don’t know if I’m reading it in the way it was intended, but I’m laughing my ass off.

      • Cyberwolf@feddit.orgEnglish
        34·
        24 days ago

        I don’t know if this is Windows trying to stop hemorrhaging users to Linux, but if they go ahead with this it will likely hilariously backfire and make multiplayer games become even more compatible with Linux.

        Steam is already rubbing their hands grubbingly.

        • Midnight Wolf@lemmy.worldEnglish
          57·
          24 days ago

          It’s MS trying to not have another meltdown like CrowdStrike. They tried to do it with Vista, and they pussied out when all the same fucks cried out ‘but we can’t fuck with the OS like a bent-over ho’, and so MS let it slide in the ‘eventually’ to-do bin until it was demonstratably their fault for not clamping down on kernel access.

          Also lol “willing to follow”, as I understand it MS isn’t giving them an option or opinion this time around. Gtfo of the kernel or your shit will stop working. I think the deadline is 2026, but it’s been a while since this was all announced.

      • sp3ctr4l@lemmy.dbzer0.comEnglish
        29·
        24 days ago

        I fucking called this after the Crowd Strike catastrophe.

        MSFT would start massively reworking their entire concept of who actually gets kernel access, because uh, causing a Y2K event is uh, really bad, actually… and yep, that probably means the kernel level AC paradigm is no longer workable.

        Fucking obviously duh, wow, turns out just letting any old ‘vetted’ vendor submit goddamned kernel level code updates without being strenuously verified each time is a bad fucking idea, wow, who could have guessed??!?