Nope. I don’t talk about myself like that.

  • 1 Post
  • 492 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle


  • Stopping processes is actually a user space action.

    Now you backpedal and say

    Pretty much all code is making requests to the kernel.

    But I don’t know what I’m talking about? Sure. We’ll go with that if it makes you feel good. I only literally taught it at a post-grad level at an R1 institution, but what do I know.

    It’s side stepping the kernel. That’s the whole point.

    You’re getting it! Kind of at least. The anti-cheat actually modifies the kernel (in an extension kind of way, like drivers do). That’s the point though. Which seems to have repeatedly whooshed over your head. But I can only say it in so many ways and be ignored. Good luck. Hope I don’t run into your code.


  • Stopping processes is actually a user space action. You can do it without admin rights btw. Even if it popped the admin screen that’s still not a kernel level action.

    Absolutely not. Task management is the job of the operating system/kernel. You can request to end a job/task. The kernel will do it on it’s own time. UAP prompts are attempts to elevate permissions so that you can access higher kernel calls.

    https://linux-kernel-labs.github.io/refs/heads/master/lectures/syscalls.html#linux-system-calls-implementation

    https://unix.stackexchange.com/questions/111625/how-does-linux-kill-a-process

    You can make requests the to the kernel. If you have permission/ownership to the process the kernel will work through the sigterm/sigkill to meet your request. It is not a user space action at all to kill a process, you make requests to the kernel to do it. Hell in linux it’s even more obvious as you can instruct the kernel on HOW you would like to kill the task and even then it may not follow your direction. https://www.man7.org/linux/man-pages/man1/kill.1.html with kill being a kernel tool. If you spawned the process, then you have permission/ownership to the process. But my point in the previous post was that anti-cheats can reach into the system, reading dlls and such that are absolutely NOT user space to begin with, require elevation beyond user space to install.

    Yeah that it’s considered malware. I did Google it and there’s nothing saying that.

    Seriously? You can’t find anything? You sure about that? Cause I can literally pull up thousands of articles and forum threads by literally typing “is vanguard anti-cheat malware?” or “is easy anti-cheat malware?”

    https://forums.malwarebytes.com/topic/288793-easy-anti-cheat-launcher-detection/

    Heuristics detect these things for what they are. Anti-virus software have to whitelist them because people choose to play the games anyway.

    https://www.techguy.org/threads/is-valorant-vanguard-a-malicious-rootkit-or-not.1267682/

    https://www.pcgamer.com/the-controversy-over-riots-vanguard-anti-cheat-software-explained/

    The name is appropriate, because Vanguard doesn’t just sniff around for cheats when Valorant is running: It starts up with Windows and keeps an eye on other processes whether or not you’re playing Valorant at the time. […] Vanguard detects software with vulnerabilities which could be exploited by cheat makers, and blocks some of it.

    https://www.sp-cy.com/article/is-valorants-anticheat-spyware/

    Vanguard cannot be easily fully disabled since after manually quitting the process, a system reboot will be required to be able to open Valorant again.
    The EULA prevents any legal recourse against Riot Games.
    Valorant/Vanguard sends encrypted data to Riot. Which is Chinese owned by a giant corporation called Tencent.

    Let’s attack this question from another perspective. Do you trust a games developer to properly develop kernel code? Most people BARELY trust Microsoft to do it these days. And you can’t review/evaluate it yourself at all. You have no fucking clue what they’re doing and never will. We’ve seen what happens when random companies inject shit into the kernel like crowdstrike did. You think that these anti-cheat softwares are acting in your interest when they’re being implemented and paid by a corporation? How can you look at these anti-cheats that have made backdoors on systems, cause people everywhere unstable kernels/BSODs, send data about your system without permission, interacts with software on your system that isn’t their code, etc… and say they’re not malicious?



  • Source for what in specific?

    That stopping processes is a kernel action? Go ahead. Open powershell and ask it to close some other system process… The UAP prompt (if you’re on windows, linux will just fail silently most of the time unless you sudo or are root) that shows up is the kernel validating that you even have permissions to do that. The kernel handles ALL task scheduling/management. When you close something you’re asking the kernel to do it. The kernel also handles ALL file management and driver management (drivers being extensions of the kernel). So the fact that it can read other active DLLs and such hooked into other processes (say your graphics drivers) is literally proof.

    That industry agrees that it’s malware? Depends on which part of industry I suppose. But if it’s able to do all these actions at the kernel level, and attached itself it to other software to install, often doesn’t uninstall when you remove the game it was attached to, AND gets flagged by anti-viruses that don’t have it whitelisted yet… It’s definitionally malware. Go search for “Is <insert anticheat> malware”. Very few people will argue that they’re not.

    Hell it’s possible for anti-cheats to write to UEFI if they really wanted to. There’s no legitimate reason for that level of access, 0, none.






  • Malware isn’t defined by its privileges but what it does.

    Correct… and anything that intercepts all system calls and forces closed applications that it deems “not safe” even if I the user specifically run it is malware. You bet your ass they feed back information to the mothership too.

    And btw, if you’re accepting the “Spyware” moniker from the other comment chain. Spyware is a form/category of malware.

    Definition from Malwarebytes:

    Hostile, intrusive, and intentionally nasty, malware seeks to invade, damage, or disable computers, computer systems, networks, tablets, and mobile devices, often by taking partial control over a device’s operations.

    Hostile - it’s not meant to help you at all. If you’re doing something deemed “unsafe” in their eyes. They will take action up to and including stealing your money that you paid for the game. intrusive - embeds itself in the kernel Intentionally nasty - Well it’s not accidentally nasty.

    invade - attached to games with little to no input on what you’re installing. disable computer systems - specifically the software you paid for Taking partial control over a device’s operations - the whole fucking kernel.

    I’d say meeting the VAST majority of the definition and at least one portion of each category is sufficient to call them all malware.



  • I have basically a full rack of equipment. Here’s the network side of it all. My desktop is 2 SPF+ fiber connections back to the core switch. Tons of stuff in my rack is all 10gbps or 40gbps.

    Dual opnsense firewalls (top 2 slots, dual 40gbps connecting to core switches), though one is inactive until they let me buy static addresses. I run some business stuff on this. Boatloads of homelabbing and self-learning.

    If you want to do full IPS/IDS, then yes you need some horsepower. But just connection with basic rules there’s plenty out there that’s not super expensive. Ubiquiti has their dream machine line which even the “cheap” $400 one can do 10gbps (2gbps with ips, or something like that. I dunno, I don’t keep tabs on them).


    I didn’t stop any active connections/downloads happening on the network. I very likely had a gig of other stuff going elsewhere on the network.

    Their “smart-nid” is also a router… so that works too, but I don’t trust it and in my setup it’s in transparent mode.

    Edit: Formatting sucked






  • Yeah the newer they are, the more frivolous they are

    Filing for patent on a mechanic that’s been in the public for 28 years already is disingenuous as fuck. Pokemon started in 1996. The throw a ball at it thing has been out there for nearly 30 years. If you have filed a patent for it in all that time… and just now choose to. That’s just dumb. If they were to have applied for the patent the day that pokemon was thing in the USA… The patent would have expired 8 years ago. It’s untenable to accept these patents from Nintendo.