this post was submitted on 15 Sep 2024
129 points (99.2% liked)

Games

16796 readers
973 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago
MODERATORS
top 5 comments
sorted by: hot top controversial new old
[–] ImplyingImplications@lemmy.ca 75 points 2 months ago

I'm glad Microsoft realized allowing any company to push kernel-level code to consumers was a terrible idea. A bug at that level can brick a PC and needs to be thoroughly scrutinized before being pushed out to end users. If a company dedicated to computer security wasn't doing proper code reviews I really doubt game studios were either.

[–] itsgroundhogdayagain@lemmy.ml 29 points 2 months ago (1 children)
[–] atro_city@fedia.io -1 points 2 months ago

Hooray for boobies!

[–] tal@lemmy.today 28 points 2 months ago* (last edited 2 months ago)

locking down the Windows kernel in order to prevent similar issues from arising in the future. Now, according to a Microsoft blog post about the recent Windows Endpoint Security Ecosystem Summit, the company is committing to providing “more security capabilities to solution providers outside of kernel mode.”

So first off, from a purely-technical standpoint, I think that that makes a lot of sense for Microsoft. Jamming all sorts of anti-cheat stuff into the Windows kernel is a great way to create security and stability problems for Windows users.

However.

I don't know if my immediate take would be that it would permit improving Linux compatibility.

So, from a purely-technical standpoint, sure. Having out-of-kernel anti-cheat systems could make it easier to permit for Linux compatibility.

But it also doesn't have to do so.

First, Microsoft may very well patent aspects of this system, and in fact, probably has some good reasons to do so. A patent-encumbered anti-cheat system solves their problem. But that doesn't mean that it's possible for other platforms to go out and implement it, not for another 20 years, at least.

Second, it may very well rely on trusted hardware, which may create issues for Linux. The fundamental premise of a traditional open-source Linux system is that anyone can run whatever they want and modify the software. That does not work well with anti-cheat systems, which require not letting users modify their local software in ways that are problematic for other users. My Linux systems don't have ties up and down the software stack to trusted hardware. Microsoft is probably fine with doing that, on both XBox and newer trusted-hardware-enabled Windows systems.

Fantastic. Though, I have to wonder if this is going to result in either way more cheaters, or if the anti-cheat will become super fucking awful to deal with and start making (broader) arbitrary decisions on what you can and cannot run because it has less access to shit.

Regardless, the less shit fucking around in the kernel the better, especially for shit that shouldn't have ever been there in the first place.