this post was submitted on 18 Nov 2026
91 points (96.9% liked)

Linux

15530 readers
307 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
 

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.

all 32 comments
sorted by: hot top controversial new old
[–] Einhornyordle@feddit.org 9 points 1 day ago

Nobara already deployed their anti cheat kernel about a month ago, it's a separate boot option in grub for me.

I've already decided to never use it and just treat anticheat for what it is: A filter to make bad games unplayable on Linux. Although I'm 100% certain that it does not matter since most casual linux games could not care less about giving up the freedom that makes Linux special just so they can continue to suck at their favourite pvp games and feel good for sometimes managing to reach worthless virtual ranks which is probably the only thing these tryhards ever accomplish in life.

[–] bitfucker@programming.dev -1 points 15 hours ago

I have no qualms with the kernel level anti cheat if they want to it to be a whitelist. But please make it open source as Tivo does. This is precisely Tivoization.

[–] andyburke@fedia.io 68 points 1 day ago (1 children)

Cheat detection belongs on the server, where there is at least some semblance of control. You can never trust the client, ever.

All this bullshit you see here ("a signed kernel and modules, TPM 2.0, Secure Boot and measured boot, IOMMU, kernel lockdown in integrity mode, kexec disabled, and BPF LSM") is security theater that's led to lots of complexity and bullshit because people keep trying to make untrustworthy clients trustworthy instead of just assuming they never ever will be.

It's all fucking ridiculous and it puts every client machine at higher risk.

Analyze the data streams the clients are sending you, classify them for risk, analyze suspicious ones further, take action. Why the fuck do people think "just one more kernel-level system, bro" is gonna fix this shit when you could actually address the problem?

[–] TwilightKiddy@scribe.disroot.org 5 points 13 hours ago

Because the real goal is not to get rid of the cheaters, but to condition people to accept that giving up control over your own device to a third party is acceptable.

Oh, the tinfoil hat? Yes, I can make you one, too.

[–] entwine@programming.dev 39 points 1 day ago (1 children)

Install kernel-level vibe coded slop to play a dying game from a dying company led by a billionaire with severe AI psychosis? No thanks lol

[–] trojanbark@lemmy.world 10 points 1 day ago

Verbatim my thoughts when I first heard about this

[–] gwheel@lemmy.zip 40 points 1 day ago (2 children)

I'm pretty sure bazzite is the well-known signer in this context. They aren't giving EAC kernel level access to bazzite, EAC is trusting that kernels signed by the bazzite team don't contain cheats.

[–] Lojcs@piefed.social 3 points 1 day ago (1 children)

Isn't running a bpf essentially the same?

[–] gwheel@lemmy.zip 3 points 1 day ago

The LSM BPF does sound bad, but I don't have my head fully wrapped around what it means or is capable of yet. My point is that this bazzite update is not describing a 'whitelist system for kernel level anticheat'. It doesn't sound like bazzite is making any change other than adding a status checker for things bazzite always supported.

[–] bjoern_tantau@swg-empire.de 6 points 1 day ago (1 children)

Yeah, most of the requirements should be default security practices anyways. I like that we now have a reason to make secure boot and TPM work properly out of the box.

[–] TwilightKiddy@scribe.disroot.org 4 points 13 hours ago

TPM is a joke of a security device and I would like to keep using secure boot with my own certificates, not the ones some unknown actors generate that could very well use just "4" as a private key. But that never happens, right?

[–] CubitOom@infosec.pub 39 points 1 day ago (1 children)

Fuck kernel level anticheat and all games that use it.

Boycott that shit if you care about your privacy.

[–] xxce2AAb@feddit.dk 37 points 1 day ago

I guess that's a thing for anybody willing to let something like that run on their machines.

[–] eleijeep@piefed.social 20 points 1 day ago

And are there zero working cheats in Fortnite as a result of this software?

[–] the_riviera_kid@lemmy.world 11 points 1 day ago
[–] lntl@lemmy.sdf.org 5 points 1 day ago (1 children)

i mean, if you're into that sort of thing... then fine? for ppl like me theres always

sudo sysctl -w kernel.unprivileged_bpf_disabled=1

No, I don't think this would work. This disables bpf for non root users, but the anticheat, if running as root, would still be able to use bpf (bpf is a framework for executing code in the kernel level).