Quote:
Originally Posted by Qtx
Windows hypervisor has been broken by exploits on numerous occasions. There was this one a few months back but that was the host access the guest. Although the idea behind hypervisors is great for protection, they can have their own problems too.
From 2012 |
Unsure if you read but I said that it won't be running inside a Windows hypervisor. I'm not using a hypervisor for security but because you need a hypervisor to run VMs on.
It'll actually be running on a dedicated ESXi host, whose other guest OS are a couple of proprietary Linux-based VMs along with a very cut down proprietary Linux OS and a ridiculously basic Linux OS that does nothing but emulate a WAN.
Even if a nasty is able to log into one of the *nix VMs as root it just gets that one machine. That host has access neither to the Internet or to the rest of my LAN as it sits in an isolated 'DMZ' VLAN which has no routing outside of the VLAN and no access to its first hop router besides DHCP and DNS.
Better not to mix the home network and the lab network.