So...
It seems little Tim Sweeney has seen the error of his ways and has not only released a native EGS application for Linux (vibe coded - yep, Epic brag about it, and it's buggy as hell at this point in time; but it is an extreme alpha release), he's also on track to release EAC v2 for Linux - which is as close to not quite kernel level anticheat as we're gonna get under an open source OS (and as close as I'm comfortable with), and something I personally see as a good thing that can only help to overcome a 'major' hurdle regarding games and Linux support - Even Fortnite is coming to Linux (gasp!).
Secure boot needs to be enabled, TPM 2.0 needs to be enabled, and IOMMU needs to be enabled. I've just spent some time updating my motherboard's BIOS, enabling all three and forcing KDE Neon to register a key regarding my Nvidia dkms drivers via an MOK password (otherwise I can just run the latest officially signed 595 drivers). All is good on my system now, Secure boot, TPM 2.0 and IOMMU are all enabled and I'm ready to go.
EGS launcher for Linux (be warned, it's really buggy at this point in time, Lutris may be a better solution for now):
https://store.epicgames.com/news/epic-games-launcher-preview
News here:
https://onlineservices.epicgames.com/news/introducing-easy-anti-cheat-linux-v2
NOTE: While this implementation doesn't run 'entirely' in user space, it's not kernel level anticheat as implemented under Windows by basically using a kernel level driver running as a rootkit:
Furthermore, it's not forcing specific kernels, the only requirement is a kernel signed with a well known key. Ubuntu and it's derivatives come by default with a signed kernel using a well known key, as do many other distro's. Arch, however, is going to be a problem unless Arch devs start signing kernels with a common key. Setting everything up under a distro based on Ubuntu LTS is trivially simple.
It seems little Tim Sweeney has seen the error of his ways and has not only released a native EGS application for Linux (vibe coded - yep, Epic brag about it, and it's buggy as hell at this point in time; but it is an extreme alpha release), he's also on track to release EAC v2 for Linux - which is as close to not quite kernel level anticheat as we're gonna get under an open source OS (and as close as I'm comfortable with), and something I personally see as a good thing that can only help to overcome a 'major' hurdle regarding games and Linux support - Even Fortnite is coming to Linux (gasp!).
Secure boot needs to be enabled, TPM 2.0 needs to be enabled, and IOMMU needs to be enabled. I've just spent some time updating my motherboard's BIOS, enabling all three and forcing KDE Neon to register a key regarding my Nvidia dkms drivers via an MOK password (otherwise I can just run the latest officially signed 595 drivers). All is good on my system now, Secure boot, TPM 2.0 and IOMMU are all enabled and I'm ready to go.
EGS launcher for Linux (be warned, it's really buggy at this point in time, Lutris may be a better solution for now):
https://store.epicgames.com/news/epic-games-launcher-preview
News here:
https://onlineservices.epicgames.com/news/introducing-easy-anti-cheat-linux-v2
NOTE: While this implementation doesn't run 'entirely' in user space, it's not kernel level anticheat as implemented under Windows by basically using a kernel level driver running as a rootkit:
On Windows, we rely heavily on a kernel driver to protect the games. This driver isn’t always on, it starts when a game is launched and stops when the player exits. For EAC Linux v2 we will not leverage an equivalent kernel module, and instead we’ll take full advantage of existing Linux platform security features like measured boot, the kernel lockdown LSM, and IOMMU support, plus our own eBPF logic to maintain integrity and detect cheaters. These security features are not available on every distro and may require configuration changes to activate.
Furthermore, it's not forcing specific kernels, the only requirement is a kernel signed with a well known key. Ubuntu and it's derivatives come by default with a signed kernel using a well known key, as do many other distro's. Arch, however, is going to be a problem unless Arch devs start signing kernels with a common key. Setting everything up under a distro based on Ubuntu LTS is trivially simple.