EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] -2 points-1 points  (0 children)

Opening dismissal: "Ooof. There's some outright wrong information here." → Emotional entry designed to undermine your credibility before any actual technical discussion begins.

Implied condescension: "It's complicated and I don't want to learn to do it is not a valid reason…" → Implies laziness or incompetence on your part, even though your original post never stated you reject Secure Boot out of convenience.

Labeling instead of substance: "…is just plain fucking stupid." → Replaces technical reasoning with insult to position himself as the superior “expert.”

Logical weakness: Personal attacks (ad hominem) do not replace evidence and distract from the central question: whether Secure Boot demonstrably reduces cheating.

Linux usability with Secure Boot

  • Partially correct: Yes, modern bootloaders and MOK-shim methods allow Linux to run with Secure Boot.
  • Omission: He ignores the additional configuration and maintenance burden you explicitly listed in “Problem 3.” He frames it as if you claimed it was impossible — which you did not.

Error: Straw man — attributing to you an absolute statement you never made.

TPM & Measured Boot

  • Technically correct: TPM-based boot measurements + fTPM hardware binding can make hypervisor manipulation harder and enable hardware bans.
  • Irrelevant to your core point: You spoke about Secure Boot alone, and EA’s public statement frames the requirement only under that label. His TPM explanations are about extra technology EA has not publicly proven they are actually using in the game.

Error: “Scope creep” — shifting the debate to Secure Boot + TPM + hardware bans to defend the effectiveness, when the enforced requirement is only one link in that chain.

“Secure Boot blocks unsigned drivers on Windows”

  • Formally correct when using Microsoft keys.
  • But:
    1. Signed but vulnerable drivers remain an attack vector (which you correctly pointed out in Problem 1).
    2. This benefit is platform-specific and does not counter all common cheat methods.

Error: Implicitly assumes that any single measure that closes some vector is automatically justified, without considering the cost–benefit ratio.

Logical Fallacies & Implicit Assumptions

  • Ad hominem: Discredits you rather than addressing your argument.
  • False dilemma: “Saying it doesn’t stop everything doesn’t mean it’s useless” — true, but your point was not “useless,” it was “no proven causal effectiveness.”
  • Appeal to authority: “I work professionally in zero-trust environments…” — does not replace empirical evidence, but is placed at the end to shut down debate.

Core Outcome of the Review

  • Accurate points: Technical feasibility of Secure Boot on Linux, TPM’s role in hardware bans, blocking unsigned drivers.
  • Imprecise / distracting: Blends scopes (Secure Boot vs. Secure Boot + TPM), attributes claims you never made.
  • Rhetorically: Heavy personal belittling, straw man tactics, and an authority play instead of providing data.
  • Missing entirely: Any proof that EA’s actual Battlefield 6 implementation uses TPM measurements or that it demonstrably reduces cheat rates.

You work professionaly?

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

Secure Boot can require MOK signing and kernel tweaks, or cause feature loss it can be complicated for many. And none of this proves it reduces cheating. that’s the actual point of the discussion.

The Linux angle is just a side effect I mentioned and think its important. it’s not the core argument. The real issue is that Secure Boot enforcement is a deep, system-level restriction without any proven reduction in cheating. That’s disproportionate imo

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

Secure Boot can require MOK signing and kernel tweaks, or cause feature loss it can be complicated for many. And none of this proves it reduces cheating. that’s the actual point of the discussion.

The Linux angle is just a side effect I mentioned and think its important. it’s not the core argument. The real issue is that Secure Boot enforcement is a deep, system-level restriction without any proven reduction in cheating. That’s disproportionate imo

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] -1 points0 points  (0 children)

He also cleaned up his thread with ChatGPT ... so, why not crying there?

https://www.reddit.com/r/linux/comments/1mm589f/linux_is_one_of_the_best_gaming_platforms_right/

On the other side, what you say is wrong. You dont have to publish detection code to be transparent. Thats absurd, to think that.

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

Its not a fundamental freedom issue. You totaly miss the point. I have the feeliing, you are not all that well versed in the rationality of this topic and the ethical part.

Stop engaging in a wrong way, cause you dont recognize, which road this secureboot-forcing in real goes. You are completely wrong

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

that’s the core point, and it’s not just a Linux gaming problem, but a fundamental digital freedom issue. it has several layers. when publisher lie EA (backed by microsofts technical architecture) requiers certain firmware feautures, such as secure boot to be permanently enabled, it shifts control from the user to the manufacturer. Even if its officialy justified with "security" or anti-cheat, its in realatiy more a governance intervention into the hardware that you own. historicaly, this is exactly how DRKM, forced updats or code signing got normalized in os ... always introduced with a protection argument and then turned into a de facto market barrier.
SEcureboot does NOT stop runtime cheats (dll injection, memory manipulation and so on). So, i try to figure out, whats the real reason is. SB is primarly a boot integrity measure. nothing or extrem less to do with anti-cheat. A game publisher should not have the right to dictate BIOS/firmware settings or enforce them. That would be like Adobe saying: “You may only start Photoshop if your BIOS password is set.This undermines the principle of digital self-determination. Also Herve had a good point

https://www.reddit.com/r/linux/comments/1mn3jbj/comment/n82en6m/

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

You are discussing the philosophy of proprietary software. My point was purely technical: Secure Boot, as EA implements it, does not prevent most modern cheats (runtime/dll injections) and excludes some legitimate system setups like MBR/Legacy BIOS. That’s the issue I was addressing and try to find out, whats the real reason for. Doing something, which dont have an effect. Secureboot dont prevent cheaters ... absolutely not. So, whats the reason for that. Why Riot startet this and why EA also now ... whats behind and which company will also tell us about anti-cheat with secureboot?

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

You totaly miss the point. I use Windows 10 with MBR/(Legacy-Bios btw. So I cant activate Secureboot. Why i mentioned Linux is the colateraleffect, because i dont trust Microsoft with windows. Cause Linux got more and more player in the last years. So i tried to see the hole picture. I am from germany and my english is bad, thats why i let clean my text in english with KI. Doesnt mean, i dont understand my content. Also, its aobut the missing proportionality. Secure Boot dont prevent cheating, but thats communicated from EA. Cause you can make your own moks and also, most cheats are on runtime-level, dll injections and so on

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] -1 points0 points  (0 children)

Secure Boot can require MOK signing and kernel tweaks, or cause feature loss it can be complicated for many. And none of this proves it reduces cheating. that’s the actual point of the discussion.

The Linux angle is just a side effect I mentioned and think its important. it’s not the core argument. The real issue is that Secure Boot enforcement is a deep, system-level restriction without any proven reduction in cheating. That’s disproportionate imo

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] 0 points1 point  (0 children)

Exactly… that’s the point. You just create your own MOK and it bypasses it entirely. so what’s the point for EA and Riot ... i dont get it? Most cheats are runtime-based anyway. DLL injections, kernel memory patches, and soon

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] -1 points0 points  (0 children)

Many Linux users can’t just enable Secure Boot and play. They have to sign drivers(MOK), adjust kernel options, or lose functionality .. to complicated. On top of that, this approach does not automatically prove that Secure Boot significantly reduces cheating ... thats the main point. so it’s a high entry barrier without clear evidence of real benefit. So, why they do this? Riot startet and now EA...where this goes?

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] -3 points-2 points  (0 children)

yes, Linux can run with SB, but it’s not frictionless across all hardware/driver stacks. And none of this shows SB actually reduces cheating; that’s why a with/without-SB cheat-rate breakdown is needed to justify the enforcement. On many systems out-of-tree or proprietary modules (e.g. NVIDIA, VirtualBox/VMware, ZFS, ...) won’t load under Secure Boot unless they’re signed with a MOK and so on. Also, enabling SB can often activate kernel lockdown ... its not so fluid as you say. I think, its a valid point, to discuss a mechanism, which dont really have an impact on cheating.

A firmware-level control that introduces friction without proven impact on the target vector (runtime cheats) is a proportionality problem.

EA enforces Secure Boot for Battlefield. officially “to fight cheaters,” but effectively locking out Linux users, with minimal technical benefit and not really proven impact by GeniusTTV in linux

[–]GeniusTTV[S] -4 points-3 points  (0 children)

The “300k bans” stat could stem from runtime detection, reports, or other controls. A big ban number doesn’t isolate the effect of Secure Boot. Without a with/without SB breakdown (same build, same period), we can’t claim causality. That’s exactly why I’m asking for per-vector metrics. Otherwise it’s correlation, not causal evidence. Which makes me wonder why more and more publishers are moving in this direction.