this post was submitted on 07 Aug 2025
37 points (93.0% liked)

PC Gaming

12027 readers
269 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] audaxdreik@pawb.social 8 points 5 days ago* (last edited 5 days ago) (1 children)

I understand your skepticism, but see my other comment on topic RE: TPM 2.0

It's basically locking down your desktop the same way your phone is locked down (unless you're one of those nerds running GrapheneOS or the likes, in which case good on ya). Theoretically this could be good in that a totally locked environment is easier to verify and shouldn't require kernel level anti-cheat anymore. But you know, at the expense of surrendering low level control of your hardware to Microsoft and the likes.

This is incredibly gross to say the least.

[โ€“] FauxLiving@lemmy.world 5 points 5 days ago

I am one of those nerds.

I also use, on Arch, btw, a TPM, and self-sign my own UKIs in order to use secure boot.

The majority of cheats which effectively evade kernel anti-cheat won't be affected. This will prevent efi cheats (cheats that load before Windows), but that's about it.

It won't prevent DMA access to memory and, unless they force using signed drivers (which, I think is a feature limited to Server packages) and only whitelisting specific hardware, something not really feasible if they want their game to run on a wide variety of computers, it's trivial to hide these cards as a NIC or other innocuous hardware.

It also doesn't prevent the aimbots that use computer vision running on external hardware because all they need to have out of the PC is display and they mimic being a mouse (another unwhitelistable piece of hardware).

What's more is that this still requires them to make kernel anti-cheat. One of the easiest ways to get access to memory is to make and install a driver. The driver isn't affected by secure boot (absent enforced driver signing, see above) and runs in ring0. The only way a game can detect that is to ALSO have software running in the kernel.

Though, to be fairrr, efi cheats are relatively simple and cheap, as they don't require extra hardware. So, it may be that this is the most common kind of undetectable cheat and worth enforcing secure boot in order to prevent. But the "best" cheats, DMA are unaffected. AI aimbots require cheaper hardware so they'll probably become the next most popular cheat.