• 3 Posts
  • 295 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • Fun fact: I used to work as a fraud analyst for aajor telecom company. British Indian Ocean territory islands were extremely high fraud destinations for telecom fraud. I always assumed the people there were basically making ends meet through fraud. (Usually hacking corporate PBX systems and directing phone traffic to premium rate service lines there) But I think it’s more likely that the phone companies there aren’t so much committing the fraud, but facilitate it with their PRS lines where they surely keep some of the revenue generated.



  • littlecolt@lemm.eetoLinux Gaming@lemmy.worldI've got banned from Apex Legends
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    2 months ago

    From two years ago, for time context, regarding EAC in Linux:

    No. It has zero kernel access, and that’s not even possible.

    EAC has (and has had for years) a native Linux client. That native Linux client is userspace only and has zero kernel access. Before, it was only for native Linux games that had EAC, like War Thunder, 7 Days to Die, Rust (before they abandoned Linux), etc. Epic refused to allow the Linux native EAC to work with Windows EAC games through Wine/Proton. That changed last fall, when Epic made the announcement.

    Now, EAC games that work in Wine/Proton use the LINUX NATIVE EAC client, which communicates with a Linux EAC binary that each game that enables support ships, alongside their Windows EAC binary. The Steam Proton EasyAntiCheat Runtime is also required. This runtime allows the NATIVE Linux EAC client (which again, is 100% userspace only and has no kernel level access) to communicate with the Windows userspace EAC binary, to allow for a less-secure but still better than nothing EAC functionality for Windows games running in Wine/Proton.

    The exact same situation is true for BattlEye. BattlEye has had a native Linux client for years, but it was userspace only, and didn’t work with Wine/Proton games. Now it does, in the same way EAC does.

    This is also why so many games are refusing to enable it. Because it’s inherently less secure against cheaters than the kernel-level EAC/BattlEye Windows implementation. Just read 343’s Destiny 2 comments from the past week and you’ll see that exact reasoning. And I (and others) said from the beginning when it was announced last fall that many games would in fact refuse to enable EAC/BE support because of the less secure nature and increased risk of cheaters. And I was right.