• Alex@lemmy.ml
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    4
    ·
    10 days ago

    Kernel access isn’t needed if they use signed boot and can verify everything running is what it should be.

      • Alex@lemmy.ml
        link
        fedilink
        English
        arrow-up
        13
        arrow-down
        1
        ·
        10 days ago

        You want to be sure if the integrity of the binaries that are running. That needs a chain of trust from firmware to user space.

        • RamRabbit@lemmy.world
          link
          fedilink
          English
          arrow-up
          66
          arrow-down
          1
          ·
          edit-2
          10 days ago

          ‘Never trust the client’, an adage that modern game developers have apparently forgotten. The only thing one can ultimately trust is the server. Anything client-side, beyond keeping honest people honest, is doomed to failure.

          Regular (ie, not kernel-level) anti-cheat is as far as it needs to go. Anything delving past that, such as into kernels, is dumb and an increasing level of security risk for the consumer.

          • sp3ctr4l@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            12
            ·
            edit-2
            10 days ago

            Kernel level AC only makes sense if you’re not selling games, you’re selling platforms for micro transactions.

            They don’t give a fuck about a ‘true’ gameplay experience.

            They do give a fuck about not being able to groom children into gambling addictions later in life, and making astounding amounts of money while doing so.

          • SorryQuick@lemmy.ca
            link
            fedilink
            English
            arrow-up
            3
            ·
            9 days ago

            Maybe so, but kernel cheats these days are extremely easy to make, even more so on linux (since you can just hotload them at will while windows whines about signing).

            ‘Never trust the client’ does very little to prevent automation and aimbots.

            In league of legends for example, kernel cheats that auto-aim your skillshots and automatically walk out of the enemy’s were really common, especially in high elo, and there is nothing the server can do to prevent them. I’ve seen my fair share of cheaters around GM elo over the years, but now, I don’t think I’ve seen a single one since they added vanguard. Though it does suck that I still need a windows partition.

          • creed10@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            8 days ago

            I’m sure the biggest reason is because running server side anti cheat is much more expensive for them, so they push the burden of computing power onto the consumer instead of footing the bill themselves. I’m sure there are also more nefarious things going on, but ultimately it all comes down to money if you think about it

        • yucandu@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          10 days ago

          Why care about the binaries when you can have AI write you a script for an ESP32 to scan a video camera and mimic hardware mouse inputs?

      • Alex@lemmy.ml
        link
        fedilink
        English
        arrow-up
        5
        ·
        10 days ago

        The chain of trust will depend on the hardware. I would expect on a Steam Deck it would be Valve all the way. If it was Ubuntu it would be Microsoft then Canonical. I doubt any random distro would be acceptable to the games wanting to enforce anti cheat.

        • Creat@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          5
          ·
          10 days ago

          You can secure boot most distros these days. It’s not new either. Depends on who it what their anchor is, and if it’s more limited than just secure boot being active.