EACv2 isn’t actually invasive in the sense how it works on Windows. It uses features we already have in Linux, without itself getting root rights or being invasive. I assume at the moment most distributions have not yet worked on this. I assume (or better hope) in the future most gaming ready distributions will have this builtin without you worrying, or enable it quickly. I think this implementation as it sounds is the best possible way, much better than how invasive anticheat works on Windows. I’m actually stoked about the way Epic handles this! It should have been Valve doing it! (And that comes from someone hating on Epic and loving Valve, BTW.)
It should have been Valve doing it! (And that comes from someone hating on Epic and loving Valve, BTW.)
I’ve written at length elsewhere in the topic about how it’s not just the technical implementation, but what this attestation process signifies about control of these companies over your system.
I understand this is one of the weaker arguments I can make in isolation, but it bears asking the question: why is it Epic that’s doing it and not Valve?
They don’t have control over my system. Its still controlled by the Linux Kernel and the features of it, no direct control from the companies. They can’t do whatever they want.
Because Valve is interested in making anticheat work in Linux. By all companies, I would have expected this from Valve. I’m not talking about working on EAC, but all the stuff how it is implemented, the work on using the Linux Kernel and setting up Secure Boot, talking with all the distributions and vendors to make it happen. And even if it was to make EAC work first, I would have expected this from Valve, because they are the most interested into all anticheats to work on Linux.
EACv2 isn’t actually invasive in the sense how it works on Windows. It uses features we already have in Linux, without itself getting root rights or being invasive. I assume at the moment most distributions have not yet worked on this. I assume (or better hope) in the future most gaming ready distributions will have this builtin without you worrying, or enable it quickly. I think this implementation as it sounds is the best possible way, much better than how invasive anticheat works on Windows. I’m actually stoked about the way Epic handles this! It should have been Valve doing it! (And that comes from someone hating on Epic and loving Valve, BTW.)
No.
I’ve written at length elsewhere in the topic about how it’s not just the technical implementation, but what this attestation process signifies about control of these companies over your system.
I understand this is one of the weaker arguments I can make in isolation, but it bears asking the question: why is it Epic that’s doing it and not Valve?
They don’t have control over my system. Its still controlled by the Linux Kernel and the features of it, no direct control from the companies. They can’t do whatever they want.
Why in god’s name should it be Valve’s job to implement this? None of Valve’s games use EAC…
Because Valve is interested in making anticheat work in Linux. By all companies, I would have expected this from Valve. I’m not talking about working on EAC, but all the stuff how it is implemented, the work on using the Linux Kernel and setting up Secure Boot, talking with all the distributions and vendors to make it happen. And even if it was to make EAC work first, I would have expected this from Valve, because they are the most interested into all anticheats to work on Linux.