this post was submitted on 18 Nov 2026
92 points (96.9% liked)
Linux
15533 readers
256 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Cheat detection belongs on the server, where there is at least some semblance of control. You can never trust the client, ever.
All this bullshit you see here ("a signed kernel and modules, TPM 2.0, Secure Boot and measured boot, IOMMU, kernel lockdown in integrity mode, kexec disabled, and BPF LSM") is security theater that's led to lots of complexity and bullshit because people keep trying to make untrustworthy clients trustworthy instead of just assuming they never ever will be.
It's all fucking ridiculous and it puts every client machine at higher risk.
Analyze the data streams the clients are sending you, classify them for risk, analyze suspicious ones further, take action. Why the fuck do people think "just one more kernel-level system, bro" is gonna fix this shit when you could actually address the problem?
Because the real goal is not to get rid of the cheaters, but to condition people to accept that giving up control over your own device to a third party is acceptable.
Oh, the tinfoil hat? Yes, I can make you one, too.