Thank you for helping to keep GamingOnLinux civil and safe!
Please tell us why you're reporting this content. Please note we store your IP address for all reports to help prevent spam and abuse. You can also email any complaints to: [email protected].
@Uso, @Shotm7 and many others who suggest custom kernels as the solution.
Custom kernels are the problem, because people can legally and practically make their own kernel, make it return whatever they want and install it on their own device.
Anti-cheat makers, which are people who are defending against the owner of the device their software is running on don't trust the kernel to help defend against its master and on Windows Microsoft at least attempts to claim that title on Linux a principled stance has been taken to not claim that title.
Yes even signed kernels are treated as suspicious UEFI level cheating already exists.
Feature wise Linux wins all the rounds in anti-cheat.
Acceptable KASLR, tainted kernels, great hardware security modules integration, etc.
This just doesn't matter, because one could've and probably someone has made a kernel that showed all the signs of having these features, but didn't actually help.
If you ask me the technical solution isn't in the Kernel at all.
It's in the things the anti-cheat developer does trust: the development tools and the trusted execution environments.
To express this belief I hereby release EASLR(Executable Adress Space Layout Randomization) under the gplv2.1 [External Link].
Edit:
Yes, I value this freedom flowing from this principled stance too and the lack of monopolistic power originating from it.
As such EASLR doesn't stop anyone from modifying anything on their computer.
It hampers undetectable mass distribution of this capability on the specific programs we're trying to protect.