Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
1. "however, all a hacker needs to do to circumvent Vanguard is to write another kernel level blob of code that loads before Vanguard"
to so this they would first need to develop a kernel driver which isn't easy as you would need to have test signing on, for it to even work
most anticheats however will not let you run their games if test signing is on
2. if you want to run a driver without test signing you will need to get it signed by microsoft which both takes time, money and they review the drivers to make sure they're secure
3. vanguard (unlike VAC) actually works enough of the time that it at least allows for peace of mind that you probably just have a skill issue
Relative to the userbase of both games what's the percentage of cheaters over there?
At the end of the day it's all that matter to the end user.
Security this security that... People already install things on their PC/Phone that are more likely to do damage than an anticheat.
the guy above talking about signing-related details might have a point BUT
i don't see why something needs to be running kernelspace code to detect cheats anyway (but i'm no expert on this)
can't the cs2 userspace code detect when other processes read/write its memory?
unfortunately, two things:
- valve is a very incompetent company
- there is a very large community of people who use valve's games and the steam platform to scam one another (so if there is a vulnerability in the client<->kernelmodule interface they will exploit it to do serious harm)
more things that are likely to do more damage => more chance of actual damage
(adding the cs2 kernel module still makes things worse even if they already had risky stuff installed)
Specifically which "vulnerabilities" are you talking about? Are you just parroting?
There's the real reason
All of the evidence shows that vanguard is significantly better than VAC currently is and even was during VAC's prime. VAC ban stats have been public for nearly a decade and Riot has published their vanguard stats showing a how much more. Vanguard is banning thousands of players a day, VAC barely manages to ban 50.
VAC in it's prime was doing ~800k bans a year which was split up into 4 manual ban waves throughout the year. At best 3 cheaters would spend 3 months ruining hundreds of games and then after a ban wave just buy a new acct and repeat the cycle every 3 months.
The entire point of anti-cheat is to have the highest possible ban rate in the shortest possible time.
You essentially did some "research" into the technical difference of VAC and Kernel AC without actually understanding what you're reading and ignoring the very public ban rates.
Do you think the entire AAA gaming industry adopted Kernel AC and pays $$$$ to AC companies because it's "the same"? You don't think AAA devs evaluate the difference to consider kernel AC over VAC?
You guys love to complain about Kernel AC and how Kernel access = vulnerability while you gobble down every game and software made by devs all around the world who could get instant access to everything or brick your entire PC from one malicious or oopsie update. There is no more or less vulnerability between vanguard and any of the software you install.