this post was submitted on 18 Nov 2026
91 points (96.9% liked)
Linux
15530 readers
352 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Isn't running a bpf essentially the same?
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.
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.
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?