News for hackers. Stuff that matters.

A comment on AMD Counter-Strikes Itself, Pulls Driver After Anti-Lag Feature Causes CS2 Bans. Parent comment

Re:AMD Counter-Strikes Itself, Pulls Driver After Anti-Lag F... by dotnet00 on Saturday October 14, 2023 @09:46AM (#37880441)
Valve's solution appears to be to have a "trusted mode" which rejects modifications. This is obviously a minimal barrier for malicious code, but it can reject benign code (eg Discord's in game layout).

Thus, they expect that the average user is likely to only be running "average" things like Discord and the graphics driver, which should be using the benign way of injecting themselves rather than breaking into trusted mode.

[ Parent | on HN ]
Re:AMD Counter-Strikes Itself, Pulls Driver After Anti-Lag F... by beeboobaa on Saturday October 14, 2023 @12:02PM (#37881563)
I don't know how it works in detail, all I know is that they once again banned players for something completely beneign, all the while pretending that they never make mistakes.
[ Parent | on HN ]
Re:AMD Counter-Strikes Itself, Pulls Driver After Anti-Lag F... by dotnet00 on Saturday October 14, 2023 @02:20PM (#37882861)
The point I'm making is that Valve has defined fairly clear lines in the sand for what they consider acceptable behavior from 3rd party applications and it's AMD's fault for pushing something that is not in fact benign as being benign.
[ Parent | on HN ]