kohlrak: I wonder if anyone thought about "black box reverse engineering" some of the DLLs and replacing them to get rid of the telemetry.
Gekko_Dekko: I had some thoughts about it, but as mentioned above - it would be a whack-a-mole. Say, for galaxy.dll, we had at least 3 updates thus far that required people to redownload their games solely due to internal changes of this library. So you have to patch it once, then again, then again. And keep backwards compatibility for those who live on the countryside and cant afford downloading new installers due to low speed/pricey connection.
And thats just one library that doesnt update too much. For game engines, you must verify every single patch to ensure things still work as intended.
Thus we are stuck with either making per-app firewall rules or adding whole telemetry domains to hosts.
Actually, Im genuinely interested if game engine with built-in telemetry (that doesnt have any way to opt-out for both developer and those who play the games) violates GDPR. Like... shouldnt there be some clear indication that "yeah, we collect stuff. Accept it or refund the game" on game's startup?
That's why we're talking about "black box reverse engineering." This means that you completely reimplement the functions from scratch. In this case, though, you wouldn't even have to fully implement, just drop a return code that didn't result in a crash. These apps usually don't break when there's no internet connection, so you need to find out what return code is "error" for a given function.
This method also comes with the benefit of being entirely legal to distribute, too.