More to your point, the hypervisor is OS-specific. On my end, it’s more of a skill issue but I have run into issues getting Linux virtual machine tools running outside of VirtualBox. The software was looking for explicit infrastructure I was struggling to provide. I eventually figured out qEMU, but that’s besides the point.
I’m going to counter and say that it might be possible for these solutions to work on Linux, but you will first need to satisfy the hardware requirements. Once you meet that then it’s possible to try with a Windows compatibility layer, but then you are shooting in the dark.
Lastly, while the crackers themselves have a reputation to uphold, they and their software can both be compromised. The article is very clear about the risks. Most people running Linux are not using secure boot, and the hypervisor is an unauditabe container.
More to your point, the hypervisor is OS-specific. On my end, it’s more of a skill issue but I have run into issues getting Linux virtual machine tools running outside of VirtualBox. The software was looking for explicit infrastructure I was struggling to provide. I eventually figured out qEMU, but that’s besides the point.
I’m going to counter and say that it might be possible for these solutions to work on Linux, but you will first need to satisfy the hardware requirements. Once you meet that then it’s possible to try with a Windows compatibility layer, but then you are shooting in the dark.
Lastly, while the crackers themselves have a reputation to uphold, they and their software can both be compromised. The article is very clear about the risks. Most people running Linux are not using secure boot, and the hypervisor is an unauditabe container.