If I have an encrypted Linux partition and a Windows partition that I use as a bootloader into Riot’s games, what are the drawbacks of installing their kernel level anticheat?
If I have an encrypted Linux partition and a Windows partition that I use as a bootloader into Riot’s games, what are the drawbacks of installing their kernel level anticheat?
Also note that even a dual boot system is leaky. A kernel level anticheat has enough power to do firmware upgrades on peripherals or the UEFI, so a badly behaving kernel level anticheat could easily take over your entire system in a way that can never be gotten rid of.
Anything kernel level can theoretically modify anything in your TPM too, so Linux programs that use it (admittedly I’m not sure any user program use it) could be manipulated in weird ways
In what ways? The worst it could do to the TPM directly is invalidate your secure boot unless I’m missing something.
for me that’s enough of an inconvenience to wash my hands of the whole dual-booting scenario.
Interesting. It’s weird that a kernel level program can upgrade UEFI. We run a lot of closed source kernel level stuff already. Do you have any links for further reading?
There definitely is upgrading of UEFI/disk firmware from a running Windows. So if Windows can…
Isn’t that terrifying, and rather telling? Effing Windows can edit UEFI…
Realistically a good starting point to read up on could be about admin privileges. Or ring 0 in software. It basically boils down to the fact that anything that is running as root ( or with admin privileges) can read and write to ANY file it wants to. Effectively having full control over the system.
In other words it could be used to do anything they want with your pc. An example of that actually happening is the anti Cheat that genshin impact is using because that was exploited in that way already.
I know about ring 0, I just assumed UEFI would be off the disk and inaccessible to any software.
UEFI is off disk, but it is writeable to some degree.
Recently there was a story about a hack exploiting the ability to write boot images (as in vendor screens that display during boot).
There’s also the ability to store executable code that runs even if the system doesn’t have an OS - this is ostensibly used for theft prevention solutions. Just imagine how that can be abused.
UEFI is a ******* problem. I’ve never liked it. I get why it exists, but it’s design was intentionally borked to push DRM-like control, under the guise of offering increased security. Yet we have that boot code that can be executed silently.
It would be nice to see the 80’s BIOS wars again, with an open-source UEFI organization this time.