From latest Bazzite release

ujust check-anticheat

Epic has announced that it’s bringing Fortnite to Linux and rebuilding its anti-cheat as Easy Anti-Cheat Linux v2 with Fortnite as the first pilot before it opens up to other developers.

EAC has supported Linux for years, but many games never opted in because the Linux version couldn’t offer the same protection as the Windows one. To close that gap, v2 will require a set of security features Linux already has: a signed kernel and modules, TPM 2.0, Secure Boot and measured boot, IOMMU, kernel lockdown in integrity mode, kexec disabled, and BPF LSM.

Here is the kicker:

They were kind enough to make us one of the accepted well-known signing keys.

So its a whitelist system for kernel level anticheat.

  • thingsiplay@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    15 hours ago

    What it does and need is listed at https://onlineservices.epicgames.com/news/introducing-easy-anti-cheat-linux-v2 . I thought a Kernel module is only needed to be loaded in, if its not part of the Kernel already. And the epf would just control what is in the Kernel already, with the rights it is given to, not full root access to do whatever it wants. The whole point was to not have the same control over the system as in Windows, if I understood it correctly.

    • moonpiedumplings@programming.dev
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      14 hours ago

      No, the whole point is to have the same control over your system as what kernel level anti cheat on windows has.

      Bpf is root. It’s a rootkit. Modern Linux rootkits use (e)bpf because it has more authority over the system than root itself, able to monitor/restrict/intercept what root does.

      • thingsiplay@lemmy.ml
        link
        fedilink
        arrow-up
        2
        arrow-down
        4
        ·
        14 hours ago

        No, the whole point is to have the same control over your system as what kernel level anti cheat on windows has.

        The whole point is to avoid that. There is probably a misunderstanding, either from my side or from your side. I think it is kind of a program that instructs the Linux Kernel to do something, it does not have root rights on its own. Kind of how you instruct to do Kernel functionality to delete a file with a non root application like rm file. You do Kernel access without having root access.

        • moonpiedumplings@programming.dev
          link
          fedilink
          English
          arrow-up
          8
          ·
          14 hours ago

          No, BPF is root. It’s like super ultra root. Bpf programs running in the kernel can do everything root does, and more, most notably, intercepting with and tampering with what root does/sees. There are plenty of examples of BPF being used as super root and backdoors:

          You do Kernel access without having root access.

          Okay, technically, you can do unprivileged bpf access. But the specific bpf lsm outlined in the post is not that. It is super-root.

          • thingsiplay@lemmy.ml
            link
            fedilink
            arrow-up
            2
            arrow-down
            3
            ·
            14 hours ago

            Alright then. I need to read more about this, maybe I was misinformed. But I’m not super convinced yet, maybe you are misinformed (no accusation here, just saying it could be).

            • ozymandias117@lemmy.world
              link
              fedilink
              English
              arrow-up
              8
              ·
              edit-2
              8 hours ago

              I don’t know your level of programming knowledge, but I will back up the previous poster.

              With eBPF you can add code that runs right before various kernel functions, in kernel space (what they’re calling super root)

              E.g. https://eunomia.dev/tutorials/19-lsm-connect/

              Some of the hook points currently supported by LSM include:
              
              * File open, creation, deletion, and movement;
              * Filesystem mounting;
              * Operations on tasks and processes;
              * Operations on sockets (creating, binding sockets, sending and receiving messages, etc.);
              

              The rules around eBPF are more for preventing a process from locking up a kernel thread than what it can access

              It was originally created for high speed routing where making decisions about where network traffic goes was too slow in userspace, but they didn’t want a completely custom kernel module