安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
The specified service does not exist as an installed service.
While you are 100% correct all of these large games do utilize KL AC's.
The program / peoples concerns lies in the ♥♥♥♥ code the developers can POSSIBLY write that allow for exploitation beyond the game to get SYSTEM user privileges on peoples computers.
Look at how many KL exploits have been utilized in malware campaigns. (These kernel exploits many time aren't even from game devs themself)
People used it for all sorts of malware campaigns, and video game cheats.
MSI AfterBurner's KL driver, GigaBytes KL driver (massively exploited, still can be), Resource Hacker's KM drivers.
It is an issue giving Kernel -> UM communications when things aren't sanitized properly. Which they are not many times.
TL;DR: Kernel ACs are *typically* fine. But there issue is always there,
Calm down, its way less scary than you think.