Re: RGB Peripherals Are A Red Line For Windows Anti-Cheat Software Now
Lawrence D’Oliveiro <[email protected]>
| Newsgroups | comp.misc |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
On 23 Aug 2026 23:13:31 +0100 (BST), Theo wrote: > Lawrence D’Oliveiro <[email protected]> wrote: >> >> Actually, no it wasn’t. The article goes on to make an educated guess: > > Actually it was: > https://windowsforum.com/windows-news.4/kb5121003-remove-inpoutx64-to-fix-arc-raiders-crashes-megathread.442938/ > > inpoutx64.sys is an _ancient_ driver that allows userspace to poke > any hardware. How is this different from, say, libusb on Linux? > Of course that blows through lots of security barriers. Not if the I/O access is itself protected behind suitable privilege protections. Again, there is a mechanism for this under Linux <https://manpages.debian.org/ioperm(2)>. > First they used InpOut32 but it was blocked by anti-cheat, then it > was WinRing0 and now it's InpOutx64. History keeps repeating. Basically, on Windows, they cannot allow the user to do anything that might require privilege on their own machine, because that could be considered in some way “cheating”.