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.
My understanding is that there’s a systemd service that runs only when the game runs, and that uses ePBF to restrict read/write access to the game files while it’s running (to prevent tampering). The tpm/secure boot/recognized kernel part is to make sure the user doesn’t have a modified kernel that will lie to the anti-cheat.
If everything works like they say, they shouldn’t have access to the non-game files and no direct kernel access. So privacy should be maintained, and theoretically no risk of a EAC bug or exploit causing a full system crash.
Overall it sounds much better to me than windows anti-cheat, but that’s a pretty low bar.
If true that does sound like a huge improvement over the Windows anticheat experience.
Agreed to your comment. Only problem i have with it is that i use mainline to get latest kernels, and that wont work (kernel is not signed). Other than that, sounds good tbh
Still not gonna run epic stuff, but technically it sounds good
You can have multiple kennels installed, so you could normally boot with mainline, but if you wanted to play a EAC game you could reboot with an approved kernel.
Oh i know i can. I always have latest mainline + latest supported incase i run into issues. I just dont want to reboot to play games. Might as well use windows for gaming then :)
I think all the things you are saying are just claims. As far as I understand it, this will be closed source software that runs as root, so basically it’s just trustmebro, the same as on Windows. I’m not a systemd expert, but seems challenging to fulfill the part where it “only runs when the game runs”.
The EBF module can be inspected, and EAC won’t have kernel access, so that limits it significantly. Things like crowdstrike, completely hiding it’s processes, etc shouldn’t be possible without it having kernel access.
The systemd service can easily be confirmed to only run while a game is running as well. You can even restrict the service to be masked except when specific games are running.
EAC having root access is a valid concern though, it will have full access to your entire filesystem. Normally you can restrict what files a systemd service can access, so we may be able to quarantine this to block any privacy concerns. However we’ll have to wait until it comes out to know that part.
Overall it’s not perfect, but users will have much higher ability to audit it on Linux versus the Windows version.