I’m having a hard time understanding how this would work. udev will load kernel modules depending on your hardware, and these modules run in kernel space. Is there an assumption that a kernel module can’t cheat? Or do they have a checksum for each possible kernel module that can be loaded?
Also, how do they read the kernel space code? Userspace can’t do this afaik. Do they load a custom kernel module to do this? Who says it can’t just be replaced with a module that returns the “right” checksum?
For example, maybe branching is something you’d like to be able to do without it being a nightmare?
Services are automatically restarted. There is no automatic reboot by default, but that can be enabled if you really want to. Otherwise it’ll keep track of whether a reboot is necessary or not.
I’ve been running Debian stable with unattended-upgrades on servers for years and have had no issues whatsoever.
European here, I suggest Bosch or Electrolux, if that’s available in your part of the world.
Jeans in the dryer? They’ll definitely shrink that way.
Word. First thing that gets installed by me on any windows install.
European here. Most of what I need are within 2 miles, so for most things everyday I ride a bike. For things further away, there’s great public transportation. For when we need to transport bigger things or go where it’s hard to go by public transport, we do have a car. However, the car gets used at most once per week.
We wouldn’t strictly need a car either. There’s several car pools around where you can book a car for a few hours when you need it.
Let me present to you:
Re: the image in this article:
Why are these QFP chips through-hole? Looks like the bastard child of QFP and DIP.
Under Santa’s hat
Ah, so they don’t actually say that they read kernel space. They check the version of all installed packages and checksum the installed DLLs/SOs.
If the user still has root privileges, this may still not prevent sideloading of kernel modules. Even if it would detect a kernel module that has been sideloaded, I believe it’s possible to write a kernel module that will still be resident after you unload it. This kernel module can then basically do anything without the knowledge of userspace. It could for example easily replace any code running in userspace, and their anticheat would miss that as it doesn’t actually check what code is currently running. Most simply, code could be injected that skips the anticheat.
Of course, in their model, if a user isn’t given root privileges it seems much harder to do anything, then probably the first thing you’d want to look for is a privilege escalation attack to obtain root privileges. This might not be that hard if they for example run Xorg as it isn’t known to be the most secure - there’s a reason there’s a strong recommendation to not run any graphical UI on servers.
Another way if you don’t have root is to simply run the code on a system that does but that does have such a kernel module - or perhaps modify the binary itself to skip the anticheat. I don’t see anything preventing that in their scheme.