• saigot
    link
    fedilink
    arrow-up
    3
    ·
    8 months ago

    Isn’t this the same anticheat that just caused that big Apex Hack? Seems like… poor timing

    • ILikeBoobies
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      8 months ago

      Kind of, the hack was through Apex’s implementation/calls to the anti-cheat

      It shouldn’t have an impact in this game

        • ILikeBoobies
          link
          fedilink
          arrow-up
          1
          ·
          8 months ago

          Not yet, EAC and EOS have stated their investigations have not found the vulnerability on their end. Respawn has yet to comment on it at all

          • c10l@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            8 months ago

            Ok so it’s unknown.

            Whilst I agree that it’s unlikely that it was an RCE in EAC like it’s been floating around, nothing can be entirely discarded yet.

            I do agree that it’s likely safe to play Halo, if the hack happened due to calls made from Apex to EAC, that means EAC’s APIs made it possible (still unlikely to be an RCE though). With that in mind, bugs or malicious code in any game that interacts with the EAC APIs could cause the same issue.

            This is one of the dangers of kernel-level anti-cheat systems.

            It should be safe® on Linux though, as it has no direct access to the kernel.

    • c10l@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      It’s not clear (to me) if EAC was a factor in the hack.

      Regardless, on Linux it runs in Proton so it should be entirely in userspace. In Windows it runs in the kernel which makes it a lot more dangerous.