516
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Oct 2026
516 points (99.6% liked)
PC Gaming
15716 readers
708 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 3 years ago
MODERATORS
The existence of it also adds another potential attack vector for hackers. It's unlikely that this would be a real problem, but any additional software is just another place that could be exploited.
Thats a really good point, especially with the more obscure modules.
It must be interesting for steam to develop a hackable device in a market that usually locks their hardware down so aggressively.
I mean just because steam doesn't mind you tinkering with their own hardware doesn't mean they should not try to secure the base system OS against outside intrusion (like a RAT entering in via an AUR installation using modules as an entry point)
Yeah, sorry I meant more in the way that a user in a VM is a really different threat surface to a full root user.
For sure both should apply security patches, and avoid malware, I'm just wondering even within that model what the differences are.