Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
If you follow the above your chances of getting a virus on a Linux based system are as low of not lower than if you were running Windows with an AV installed.
Regardless of OS best antivirus is prevention, if you need an AV to clean up after it's too late you've already lost so just use common sense, only click trusted links, keep your system and programs up to date, use strong passwords and you'll be good.
Mac/iOS/Android doesn't need one either, Mac maybe you can run a scan on sometimes if you download unsigned software outside the App Store but it's likely not necessary, android and especially iOS due to how much different the OS handles these things it's literally impossible to get malware (unless you have rich hackers or the government after you willing to spend millions on the latest 0 day exploits), real antiviruses like you see on Windows don't even exist for mobile because they're completely unnecessary.
Most attacks you should worry about happen online that try to steal your various account logins and sensitive information from them so again focus more on using strong passwords, two factor login, locking down your privacy settings, use an adblocker to prevent malicious ads and phishing sites from loading etc.
What you should be concerned about instead is someone tricking you into running commands that will do bad things, especially if that command starts with "sudo"
You also might want to check out Linux-based security concepts like hardened kernels or things like apparmor, but be aware that this is more advanced and may lock down elements of the OS that your particular distro might need to run. This requires some learning and research and isn't fire-and-forget. Linux is highly configurable so there's less of a straightforward answer.
I think your best practice is to back up your documents (your steam games are already backed up) and know how to wipe the Deck and restore it to factory. If you use it for more than just a game platform, I would consider taking further steps.
This is my personal perspective. I'm not a malware specialist. And new exploits are discovered daily so the future may be different. Of course, Steam OS 3.x will be altered over time as well.
The weakest attack vector isn't the Linux OS, it's the applications & their users -- such as web browsers javascript engines (don't visit shady pirate sites.) So, only install trustworthy flatpaks from their project owners. If you're scripting, you'll likely know what you're doing. Scripting language logistic paths are also becoming a focused attack vector.
**IF** by chance malware does land on your Deck (would that be called an SDI XD ) here's the deal:
* By design, both rootfs file systems are read-only. This is how Linux based appliances work. If one fails, fall back to the other. Both will be read-only. All directories that must maintain a read-write state should be on an Overlay filesystem OR mounted from another location (bind mounted or logical volume). Nuke those read-write spaces and you go back to factory default state. This is what happens when you factory reset your Steam Deck.
* The way to change the read-only state is using a sudo command (or becoming the root user). The 'deck' user cannot do this *unless* you set a password. And then, you still must enter the password first. You can set the /etc/suders stuff to use NOPASSWD but that in bad form and you need to do it right or you'll break sudo.
So, ** I've set the deck user password in Desktop mode.** If ANYTHING attempts to sudo a command, I'll know cause I'll be prompted. sudo's default timeout is 15 minutes or so.
It's very likely in the future some Steam OS targeting malware will look for those systems without a deck password set. The malware will set it, sudo a payload download, and be persistent until the device is reset. I'm beating that future malware to punch by setting by setting my 'deck' user's password -- a strong password is important. NOTE: The PIN is not used as the 'deck' password. Besides, a numeric sequence is weak. (I hate that phones use the weakest forms of unlocking - swipes, PIN, fingerprint/faceid.)
Or course, malware could always download a payload to try and crack your deck password, but that can be a challenge to persist where it left off between reboots, the extra energy draw & heat, impact game performance, etc. I'll sense something is off more the likely.
* What about "windows" malware on Linux. Uh, Proton is like a Windows sandbox. Your Arch based Steam OS will not be infected -- just the game space. Nuke the game & proton used, then re-installe - be sure to backup your Game Saves if they don't cloud sync.
* Worse case scenario, re-image your Steam Deck and that would clear its headcold. But wait, what about UEFI malware. That is still pretty specific to Windows machines to run the payload that infects UEFI. I've done some light searching and haven't found articles on UEFI rootkits any targeting Linux.
So basically, don't use Windows on your Deck, use the Steam Deck as intended (doing nothing shady) and you should be fine.
Cheers, retro.
system issues in linux are usually consequence of a bad update with a small bug, a inexperienced user changing something critical, or a compatibility issue after an update. so, you shouldnt worry about an av.
There's always abundant of exploits no matter the os.