Steam Deck

15047 readers

164 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Follow the rules of Sopuli
Posts must be related to the Steam Deck in an obvious way.
No piracy, there are other communities for that.
Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
This is a place of civil discussion, no trolling.
Have fun.

Link to our Matrix Space

founded 3 years ago

MODERATORS

Moxvallix@sopuli.xyz

codus@leby.dev

timi@lemmy.world

RolAIDS05@lemmy.world

Fubarberry@sopuli.xyz

RolAIDS05@sopuli.xyz

345

Microsoft looking to restrict kernel level access after CrowdStrike incident might help us with our current Anti-Cheat dilemma (www.theverge.com)

submitted 5 months ago* (last edited 5 months ago) by Fubarberry@sopuli.xyz to c/steamdeck@sopuli.xyz

33 comments fedilink hide all child comments

Kernel anti-cheat systems are currently the bane of Linux/Steam Deck gaming, haven't actually proven to be effective at stopping cheaters (see Valorant for an example), and lead to various security concerns from giving 3rd parties full access to your machine to being used to install ransomware and malware.

Windows tried to restrict kernel access years ago, but backed down under pressure from various companies. However Crowdstrike's outages have shown the sever consequences of leaving kernel access open, and we might finally see kernel access to be cut off.

you are viewing a single comment's thread
view the rest of the comments

[–] GoodEye8@lemm.ee 0 points 4 months ago (1 children)

Have you considered that the reason cheaters have to go hardware level is because kernel level anti-cheats are effective at what they're supposed to do?

I'll also ask this question, what do you are the alternative solutions to client side anticheats?

[–] Fubarberry@sopuli.xyz 4 points 4 months ago (1 children)

I'm not against client side anti-cheats in general, but kernel level ones are too big of a security risk in my opinion.

The US government is banning apps like tiktok and considering banning DJI drones due to the amount of data they collect and send back to China. Several of the most popular games using kernel anti-cheat are all Chinese owned companies, and the whole point of kernel anti-cheat is that it has full access to your computer (making it hard to hide cheating). I have a strong suspicion that even if Microsoft doesn't restrict kernel access, we may see government bans on some of these games.

[–] GoodEye8@lemm.ee 1 points 4 months ago

I get the privacy issue but there's effectively no non-kernel anticheats on the market. I think VAC doesn't run in kernel level and CS is known to have a huge cheating issue, so much that competitive CS has spun off into third party provider who among other things uses a kernel level anticheat. You can't be for client side anticheat and be against kernel anticheat. Non-kernel anticheat simply doesn't do its job.

I can't imagine how Microsoft locks down Kernel so that it's also locked down for cheat developers (because they don't really care about regulations). If it's locked for anticheat developers but not for cheat developers then it's going to end up being a bad time for us.