this post was submitted on 11 Apr 2024
294 points (97.4% liked)
Linux Gaming
15335 readers
3 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm no expert here, but couldn't they rely on SEV/SME or similar? My understanding is those features encrypt RAM, which would make it a lot more difficult for an attacker to do memory-based attacks when the game is running within a VM. I expect "physical attacks" would include attacking a VM's memory, but again, I'm not an expert.
I also wonder if this could work in a containerized environment instead of a VM, so players could just run a lightweight container and preserve direct access to resources like the GPU. I don't know if GPU access can be required to be encrypted as well, but surely this is a massive step forward.
i have no clue myself frankly. Realistically, doing literally anything is probably going to be better than what riot claims is possible. I think a fundamental part of the problem is stuff outside the control of the game, the OS already has segmented ram for instance, it's all supposed to be virtually privatized, that way you don't get these kinds of problems On the fly encryption would probably help, though they would probably just use shitty encryption anyway. Regardless, if you get something to hook into the game code itself, rather than just abusing memory values, it wouldn't matter. Because at that point it's going to be running inside the game.