Unknown, but there were a few obvious bios options I saw that are needed to make the kits performant with some systems. I still find it absurd people would go that far to cheat at a game. =3
> I still find it absurd people would go that far to cheat at a game. =3
I guess it turns the cheating into its own meta-game!
Unknown, but there were a few obvious bios options I saw that are needed to make the kits performant with some systems. I still find it absurd people would go that far to cheat at a game. =3
> I still find it absurd people would go that far to cheat at a game. =3 I guess it turns the cheating into its own meta-game!
True, but a blacklisted $5k GPU seems like a bit of a risk. =3
I would recommend having a look at advanced side-channel PCIe bus DMA taps used by game cheats. They use a second computer along with an external HDMI mask-overlay mixer, to dump the target computers internal game-engine state through unencrypted DMA access to the overlay channel. Thus, gives the cheaters x-ray vision and aim-bot features for games protected by kernel level anti-cheat software. Highly entertaining nu…
Does this work with IOMMU?
it would be at a low enough level to reprogram IOMMU unless a hypervisor will prevent it.
if you have a hypervisor you can prevent the other to do the dma freely in memory because u can use iommu and things like amd-vi to separate it good. but if you dont have the hv below it, any devices with dma can do the duty across entire ram.
Blast from the past for me, though primarily interacted with the complementary Whonix side of things. Not surprising to read, considering how lean Qubes was from the get-go designed to be it makes sense that most things are from resulting upstream rather than with their code. Fully aware that it was never the goal for Qubes, but I have never been able to shake the idea that one could leverage their architecture in wa…
I had the exact same thought back in the day. The security isolation is obviously the main selling point, but the way Qubes handles seamless GUI integration across completely separate domains is technically beautiful. With modern CPUs having much better hardware virtualization support than a decade ago, building a developer-focused OS that leverages that same compartmentalization (e.g., isolating different client env…
Ehhh, I think most engineers that actually want this are pretty accepting of their current tooling and wouldn’t want to switch to a whole new Linux distribution just for a slightly more seamless experience. Besides, the people who care are always pushing forward to make the UX better — see devcontainers, Apple Containers, WSL, etc.