-
Posts
-
If you're looking for the full L2OFF source code, please contact NCsoft.😁 -
you don't need to block the adrenaline users from the start! you need to know only who use and then to ban at random time by your panel! -
Pretty much everything. I can write my own bootkit and inject whatever the hell I want to get around their protection or any usermode checks simply by hooking certain things. Most Kernel anticheats are also pretty much bypassable if you know what you're doing and how to sign a driver correctly. You can do many crazy things with it. On top of that it's easy to deobfuscate the red texts on IDA and make it readable, and in the end it's always going to have weak points no matter which one it is. 😄 Bootkits, USB injections, and other methods can be used to manipulate many anticheat systems. Honestly, Lineage 2 anticheats are some of the worst out there no one has been able to create anything truly reliable or decent yet. xD -
Test server launched, available at: Test-Server -
.thumb.png.b8c670f34de56a5b725691b17807071d.png)
I agree. You mention a lot about system calls. At which level? If your driver component runs in user mode, someone can pretty easily send whatever data he likes to the backend. Also, even if you load sys kernel driver using windows service manager, the driver still needs to be signed and comply with secure boot policy, vbs / hvci / memory integrity restrictions if those protections are enabled.
-
-
Topics
-
Recommended Posts