Tools like Battle eye and EAC are not just one tool that gives a binary answer, they are tools that detect a huge range of heuristics about the device and how easy it is to interfere with the memory.
While they have been ported to Linux, an awful lot of those bits of telemetry simply don't give the desired answer, or even any answer at all, because that is very hard to so when there aren't proprietary drivers signed down to the hardware root of trust by a third party (and certainly the average Linux user on HN wouldn't want there to be!).
It's really not a matter of "enabled by the developer", it's entirely dependent on what your threat model is.
None of this is relevant to the original point of "kernel anti cheats don't work" when yes the two most widely used ACs do work despite being kernel level.
>It's really not a matter of "enabled by the developer", it's entirely dependent on what your threat model is.
Tools like Battle eye and EAC are not just one tool that gives a binary answer, they are tools that detect a huge range of heuristics about the device and how easy it is to interfere with the memory.
While they have been ported to Linux, an awful lot of those bits of telemetry simply don't give the desired answer, or even any answer at all, because that is very hard to so when there aren't proprietary drivers signed down to the hardware root of trust by a third party (and certainly the average Linux user on HN wouldn't want there to be!).
It's really not a matter of "enabled by the developer", it's entirely dependent on what your threat model is.