| ▲ | maccard an hour ago | |
A DMA cheat requires a hardware change (and a second device). That is a much higher barrier than a download plus reboot. > you can achieve the same with user mode anticheats A user mode anti cheat is immediately defeated by a kernel mode cheat, and cheaters have already moved past this in practice. A user mode anti cheat (on windows) with admin privileges has pretty much full system access anyway, so presumably if you have a problem with kernel AC you also have a problem with user mode. Lastly, cheating is an arms race. While in theory, the cheaters will always win, the only thing that actually matters is what the cheaters are doing in practice. Kernel mode is default even for free cheats you download, so the defaults have to cover that. | ||
| ▲ | himata4113 an hour ago | parent [-] | |
this is a common misconception, just because you're in kernel-mode doesn't mean you are immediately undetected and things are not as easy people initinally think. First, point of ingress: registry, file caches, dns, vulnerable driver logs. Memory probe detection: workingsets, page guards, non trivial obfuscation, atoms, fibers. Detection: usermode exposes a lot of kernel internals: raw access to window and process handles, 'undocumented' syscalls, win32, user32, kiucd, apcs. Loss of functionality: no hooks, limited point of ingress, hardened obfuscation, encrypted pages, tamper protection. I could go on, but generally "lol go kernelmode" is sometimes way more difficult than just hiding yourself among the legitimate functionality of 3rd party applications. This is everything used by anticheats today, from usermode. The kernel module is more often than not used for integrity checks, vm detection and walking physical memory. | ||