Steam :: Steamworks Development :: New Tool for Describing Anti-Cheat in Games
steamcommunity.com
A new dedicated field helps developers describe the anti-cheat provider used in a game

Steam store pages received a new Anti-cheat field. Disclosure is mandatory for kernel-level anti-cheat solutions. And recommended for other anti-cheat solutions (like server-side or non-kernel-level client-side).

The field discloses the anti-cheat product, whether it is a kernel-level installation, and whether it uninstalls with the product or requires manual removal to remove.

Screenshot of anti-cheat indications

  • Saik0@lemmy.saik0.comEnglish
    1·
    3 days ago

    Stopping processes is actually a user space action.

    Now you backpedal and say

    Pretty much all code is making requests to the kernel.

    But I don’t know what I’m talking about? Sure. We’ll go with that if it makes you feel good. I only literally taught it at a post-grad level at an R1 institution, but what do I know.

    It’s side stepping the kernel. That’s the whole point.

    You’re getting it! Kind of at least. The anti-cheat actually modifies the kernel (in an extension kind of way, like drivers do). That’s the point though. Which seems to have repeatedly whooshed over your head. But I can only say it in so many ways and be ignored. Good luck. Hope I don’t run into your code.

    • GetOffMyLan@programming.dev
      1·
      2 days ago

      Not back peddling you are misunderstanding what kernel access means.

      You don’t need kernel level access (the thing we are literally discussing) to kill processes. Which was literally your example.

      Obviously the OS handles it. How the fuck else would it work?