Would installing an OS on an external ssd and booting into that to run pirated software while blocking access to other drives in your system or physically unplugging them be one way?
Or are there better ways to isolate the software you run and use as much as possible?
I don’t know where you guys get your stuff but if you have reasons to be this causious I would suggest having your important stuff somewhere else instead of the other way arround.
It doesn’t hurt to be cautious. Trusted sources have occasionally included malicious materials and blindsided users
Of course you have. Even with genuine, non-pirated software. Have you heard about data mining?
A(n outbound) firewall is an absolute minimum.
Depends on your threat model.
A air gap system is the gold standard.
A virtual machine is a reasonable middle ground, and of course you cut the network access.
Qubes lets you do both but it sacrifices some performance.
A word of caution about dual booting systems: if something is running on the computer, it in theory has full access to everything attached to that computer, including unmounted drives, encrypted drives, even BIOS. There are Trojans that install themselves in the boot partition, and it’s possible an infected operating system could infect the non-infected operating system next time you boot.
Threat model is just trying to lower the chances of infecting the main drive even if stuff like games or software are from a “trusted source”.
Aside from getting an enitely separate system dedicated to just running pirated games which is expensive to do.
Unmounted drives in case of dual booting still leading to infections is what made me wonder about installing an OS entirely on the external SSD and physically unplugging other drives. Of course, as you said bios is still a risk. But, more just trying to lessen chances from trusted game sources by not installing right away from release to see if anything happens to other people the first couple of weeks. And just wishing to not intermingle the two environments.
If your computer has a TPM, and secure boot, you could reasonably swap out your data drives. So you have one drive for your untrusted programs and one drive for your trusted programs. Never put them in the computer at the same time together. And that would cover a lot of the risk surface.
If you have any connected peripherals that have data storage, like fancy monitors that have a boot drive attached, or programmable keyboards, or anything like that, those are potential vectors to cross contaminate. So don’t plug those into the system with the untrusted programs
Trojans that install themselves into the MBR will just screw up your boot process on a UEFI system and vice versa. Also, if you don’t use a default bootloader, you’ll definitely notice something on a UEFI system if it tries to delete all other bootloaders.
On BIOS systems however, it gets a little tricky, since it just blindly reads the first few sectors, without respect to what you “set” as the default, so that Trojan could just add itself and move everything over a bit, and you can’t tell. See the Michelangelo MBR virus. It wiped your drive on March 6 of any year.
On a UEFI system, the best it could do is replace the Microsoft bootloader, and that would trip Secure Boot, which is enabled by default. Even then you don’t need to directly modify sectors or format your drive, you can just replace the bootloader.
Agreed it’s rare. But it exists, Moon bounce, Mosaic regressor, so if you’re trying to segment things you should just remove the drives and not worry about it.
A virtual machine would be relatively safe most of the time.
How is the performance impact these days for games compared to running natively?
Not great but better than it used to be. Don’t do a GPU passthrough.
What’s wrong with GPU passthrough?
GPU passthroughs can expose the host to a potentially compromised VM.
Interesting, do you have more information on that? Because why is GPU passthrough a problem but not other PCI devices?
I don’t unfortunately. This is from a conversation I had with a researcher in VM escape.
As far as I’m aware peripherals are not actually passed through exactly but rather emulated on the guest machine. When you pass through a peripheral you’re only passing the input of that device, data is not sent upstream.
Whereas passing through the GPU you’re providing a means of accessing non-emulated devices through the hardware itself bypassing the isolation provided by virtualization entirely.
That’s true, but the IOMMU on your host is supposed to prevent any accesses outside of the group you passed in
As long as the GPU is the only thing in that IOMMU group, you’re reasonably safe
deleted by creator
How about sandboxie ?
I would love to know the answer to that. It’s an interesting solution to be sure, but it surely has some kind of holes.
Also, it doesn’t work with electron apps. Found that out the hard way.
I just block apps in firewall. Never had problems with pirate software, only some I couldnt get working.
What are you trying to protect from?
You can also run another OS in VM, but performance is questionable.
If you are afraid of losing data, you need backup anyway
Just didn’t seem like a good idea to run pirated software of games on your primary system even if the stuff is from a “trusted” source.
Which was why I was wondering what steps people take to play games for those that try to lower the risks.
If you want to play games in VM you will probably need qemu/kvm and sepparate GPU for passthrough. Otherwise your VM will struggle to load anything serious. But I think others use that mostly to run windows apps on linux machine or simmilar. Maybe you can just dualboot from 2nd drive, it should be 100% safe if you unplug your main drive, but thats probably overkill. Im no expert, just putting it here so you can google
KVM would be a safe way to test your pirated software. But it downgrades the performance.
Not a Pirate, but I often upload stuff to virustotal.
Vitustotal uploader is the best!
Dual boot
I haven’t seen your stance on VMs, but a lighter approach might be confining the software to an AppArmor profile or such. The kernel will enforce the restrictions on what it can and can’t do.
It won’t have the overhead of virtual machines, and you can keep using a single video card, but setting this up is quite tedious, though.
