this post was submitted on 11 Apr 2024
295 points (97.4% liked)
Linux Gaming
15292 readers
6 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
Stop stealing our CPU cycles for high risk rootkits and start mitigating and detecting cheating on the server.
It's that easy.
I stopped playing games that want this bullshit. Don't need that shit in my life.
I'm guessing you're not a programmer yourself? Because it's really really not that east to /just/ detect in the server side, hacks can be super sofisticsted these days and there are often many client side exploits that you simply cannot detect serverside.
It's not easy, but it's really not worth the massive gaping security vulnerability you are giving your users. One disgruntled employee giving out the keys to the castle or one programmer plugging in an infected USB, and every user now has a persistent malicious rootkit. The only way to fix an issue that deep after it gets exploited is to literally throw away your hard drive.
This can't be right.
Don't throw your hard drive in the trash. Quarantine the infected computer, and then wipe that hoe and slap your choice of OS back on it and scan/monitor to see if any issues arise.
Edit: since folks may or may not read though the rest of the conversation: I am wrong, throw that SSD/HDD in the garbage like barbarian said.
I'm sorry to disappoint, but with rootkits, that is very real. With that level of permissions, it can rewrite HDD/SSD drivers to install malware on boot.
There's even malware that can rewrite BIOS/UEFI, in which case the whole motherboard has to go in the bin. That's much less likely due to the complexity though, but it does exist.
not all rootkits are made to do that. So yes in some cases, throw it in the trash. In others, remediate your machine and move on.
Outside of monitoring individual packets outside of your computer (as in, man in the middle yourself with a spare computer and hoping the malware phones home right when you're looking) there's no way of knowing.
Once ring 0 is compromised, nothing your computer says can be trusted. A compromised OS can lie to anti-malware scanners, hide things from the installed software list and process manager, and just generally not show you what it doesnt want to show you. "Just remediate" does not work with rootkits.
Dude... That's fucked. They should really go a little more in depth on rootkits in the CompTIA A+ study material. I mean, I get that it's supposed to be a foundational over view of most IT concepts, but it would have helped me not look dumb.
Please don't walk away from this feeling dumb. Most IT professionals aren't aware of the scale of the issue outside of sysadmin and cybersecurity. I've met programmers who shrug at the most egregious vulnerabilities, and vendors who want us to put dangerous stuff on our servers. Security just isn't taken as seriously as it should be.
Unrelated, but I wish you the best of luck with your studies!
Good morning! If anything this was a great example of not being able to know everything when it comes to IT and especially cybersecurity. Thank you for your well wishes! I earned my A+ last month and I'm currently working on a Google cybersec certificate, since it'll give me 30% off on the sec+ exam price. I really appreciate your insight on rootkits and it's definitely going in my notes!
Glad to hear it!
Just as another thing to add to your notes, in ordinary circumstances, it's practically impossible for non-government actors to get rootkits on modern machines with the latest security patches (EDIT: I'm talking remotely. Physical access is a whole other thing). To work your way up from ring 3 (untrusted programs) all the way to ring 0 (kernel), you'd need to chain together multiple zero day vulnerabilities which take incredibly talented cybersec researchers years to discover, keep hidden and then exploit. And all that is basically one-use, because those vulnerabilities will be patched afterwards.
This is why anti-cheat rootkits are so dangerous. If you can exploit the anti-cheat software, you can skip all that incredibly difficult work and go straight to ring 0.
EDIT: Oh, and as an added note, generally speaking if you have physical access to the machine, you own the machine. There is no defence possible against somebody physically being able to plug a USB stick in and boot from whatever OS they want and bypass any defences they want.
Cheers to the note as to why the anti-cheat is basically satan in software form. This is the real reason that riot isn't open to community discussion on this topic. It's indefensible... and if the userbase understood more they wouldn't have any users left.
It’s the same reason stuff like antivirus is a huge vector for attack. It runs at elevated permissions generally and scans untrusted inputs by default. So it makes for a great target to pivot into a system. These anti cheat kernel modules are no different in their attack profile. And if anything them being there is a good reason to target them you have a user that has a higher end gpu so the hardware is a known quantity to be targeted.
Hell yes I'm adding this to my notes as well, thank you!