Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Console anti-cheat wouldn't be able to detect the Cronus since it's just modifying controller inputs to help the user.

It isn't software running on the console, which is what anti-cheat generally protects against.



A lot of these Cronus-like devices do more than just translate input these days, many of them will attempt to manage weapon recoil for you (by adding downward and/or side to side input to the virtual aiming stick input at the same rate as the weapon recoil is pushing it up and/or to the sides) or generate other input intermixed with the user's input like adding very subtle circular motion of the aiming stick to try to enhance the benefit of the reticle friction aim assist that exists within the games themselves.

These sorts of generated inputs could in theory be detected using heuristics to watch for inputs that appear too patterned to be fully human. Whether any company is bothering with this, I have no idea. The only one I'm aware of that even appears to attempt to detect these types of devices at all is Epic and I have no idea what methods they use.


That's what I mean by "modifying controller inputs". All it can do is change what a controller does. They can't change the video, or affect the game logic in any way.

And it seems like it would be pretty simple to detect this in the game itself; this sort of detection doesn't need any anti-cheat with deep system hooks.


> this sort of detection doesn't need any anti-cheat with deep system hooks.

Correct, it wouldn't need any deep system hooks, nor are the console manufacturers likely to ever give game developers the ability to hook into the system that deeply, nor do they really need to since modern consoles are secure enough in practice that wallhack/aimbot type system level code cheats haven't been a concern for a while now on the major console platforms.

There are various bits of anti-cheat logic that game developers could be putting into their console version like the aforementioned analysis of input devices to look for helper devices, and things like looking for likely "lag switch" attacks by keeping track of the ongoing latency of packets coming in and out, but these are all passive heuristic checks that would exist within the game itself, not driver or kernel level anti-cheat as is common on PC.


Monitoring input is how modern anti-cheats work. They all still implement the spyware approach, but that’s really the lowest hanging fruit.


What? No.

Practically all anti cheat for a long time has primarily worked by monitoring what is running on the computer/device, and ensuring the integrity of the game and its data.

You don’t need anti-cheat with deep system hooks to monitor input. That can be done from the game itself trivially.


So how would you expect console anti-cheat to work, given that modern consoles are pretty securely locked down and don't require the rootkit approach?

I would be surprised if they aren't using heuristics on input.


Denuvo, one of the primary cross-platform anti-cheat systems, deals with ensuring the integrity of offline progress, obfuscation and encryption to prevent data mining, and emulator prevention. In their own words:

> Protect sensitive game logic to reduce data mining and detect peripherals that give the cheater an unfair gameplay advantage.

https://irdeto.com/denuvo/console-games-protection/

They also have a common list of cheats on the general information page, none of which are really related to Cronus.


No they don't.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: