- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
From the article
Microsoft has officially announced its intent to move security measures out of the kernel, following the Crowdstrike disaster a few short months ago. The removal of kernel access for security solutions would likely revolutionise running Windows games on the Steam Deck and other Linux systems.
I think I need more info. It seems like userspace is very hackable, so thus kernel level anti-cheat was born to control stuff like synthetic inputs and manipulation of memory / frame analysis. This anti-cheat would be held together by the fact that the kernel/drivers are proprietary and not very easy to edit. Obviously still possible because it’s on your own computer, but challenging and invasive. Do I have that right?
In which case I don’t see how going back to userspace would help. What is the solution? There probably isn’t one outside of hardware (buying a hacking chip and soldering it in is annoying for most)
When I was doing game dev we focussed on AI-style analytics of user behavior. Of course a good enough bot could always look human. A real cat and mouse game wasting lots of time
My guess is that Microsoft wants provide some kind of kernel level anti-cheat, possibly directly integrated with directx, and it will use cryptography which will make it impossible to emulate with Wine/Proton.
The same kernel software cryptography could certainly be marketed for single player games and proprietary applications as a solution to piracy.
Don’t like kernel anti cheat in your multiplayer games? here’s kernel anticheat for your single player games!
Removing 3rd party kernel access will probably also make cheating harder. Kernel anticheat is necessary largely in part due to cheat software using exploits in the 3rd party extension system to get kernel privileges itself and evade user mode anticheat.