The anti-cheat software is being prepared for the platform, while a native client is already available as a preview.

This article goes more into how EAC for Linux is being altered. Basically EAC can run with ring 0 access on windows machines to prevent cheats, but on Linux it doesn’t have the same level of invasive access. This is better for user privacy, but also limits its ability to prevent cheating.

The upcoming EAC Linux v2 will fall into a middle ground between the two, and will require the kernel to be signed with a key Epic recognizes. The system will also have to have TPM 2.0 and secure boot enabled. I recommend reading the article for more details.

  • mlg@lemmy.worldEnglish
    1·
    1 hour ago

    EAC Linux v2 runs a systemd service that stays active just for the length of a protected game session, alongside eBPF programs written by Epic that watch for tampering and cheats.

    For players, this means a stricter boot setup, so Secure Boot and TPM 2.0 need to be on, the kernel has to be signed with a key Epic recognizes, and several other boot and kernel settings come into play.

    EAC checks all of this only when a protected game launches, and failing the check brings up an error, not a ban. Players can also keep a separate boot entry for protected games and run their own keys elsewhere.

    So I guess MOK is not supported? That would make it impossible to play with Nvidia drivers because they need a MOK for signing.

    Using eBPF is actually a pretty neat idea, but I guess MOK would be too easy of a bypass because you can sign your own kernel modules and just do whatever in kernel space.

    It’s way better than a crappy kernel module but I wonder if hackers will actually abuse this for access over windows, especially when the Android version is also right there without any significant anticheat.