EA's Javelin Threat: Kernel-Level Cheats Force Linux Adoption, But At What Cost?
EA's pivot to Linux and Proton support, backed by advancements like Proton 11 Beta, signals major publishers view Linux as a viable, revenue stream. This focus extends to demanding kernel-level anti-cheat integration.
The reaction cleaves sharply: some see this as an economic push, with Bongles noting EA's interest proves measurable profit in the market. Others warn that kernel access grants invasive monitoring, citing 'who' that any installed malware could persist until the entire OS is reinstalled. 'sp3ctr4l' nailed the criticism, stating that kernel AC 'only makes sense if you're not selling games, you're selling platforms for micro transactions.' The technical critiques were sharp; definitemaybe outlined methods like measuring network latency to disprove client-side checks.
The weight of opinion shows a clear fracture. While some track the 8%+ Steam user growth (RamRabbit), the overwhelming concern revolves around the fundamental security tradeoff. The market appears willing to accept the invasive surveillance if it means AAA titles run on Steam Deck or mainline Linux, but the mechanism remains deeply controversial.
Key Points
EA's move to Linux proves the platform is a lucrative market segment.
Bongles argues EA's investment pressures other developers to support Linux, indicating profit motive.
Kernel-level anti-cheat poses unacceptable, extreme security risks.
who warns that persistence via kernel access makes the risk greater than the cheating problem itself.
Server-side data analysis is the superior, less invasive anti-cheat method.
tinfoilhat advocates for analyzing data streams like keystrokes and mouse movements instead of client hooks.
EA's focus is specifically on the ARM64 ecosystem, not just general Linux.
just_another_person points to the job listing's ARM64 focus as evidence of this specific market interest.
Client-side anti-cheat measures are fundamentally flawed.
definitemaybe provided a deep technical counter-argument outlining methods to counter client-side checks.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.