this post was submitted on 11 Aug 2025
175 points (97.8% liked)
Linux Gaming
20602 readers
229 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.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There are two cases.
When you run a game, the game is allowed to monitor your input (up to some configuration), so you shouldn't e.g. open a game and do online banking at the same time.
When the game installs a malicious software such that your input is monitored even when you're not running the game, then you can only rely on the additional defense mechanism. However, this is similar to all other software.
One needs to trust a game like any other proprietary software. That seems like a good rule of thumb.
I mean, once you invoke a game once outside a sandbox, all bets are off from that point on. It can modify your environment to do whatever from that point on. Like, it could, oh, modify your
~/.bashrc
to invoke some keylogger binary that it drops off somewhere in your home directory. Just closing the game isn't going to be a reliable mechanism for preventing malware in a game from dicking with the system after that point.