Linked by Thom Holwerda on Wed 28th Nov 2012 15:17 UTC
Thread beginning with comment 543578
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Owning one of the OS within a VM setup can still give a lot of leeway...
My primary purpose is software development and testing, not every day use. The most those systems use the Internet is for updating the tools using Windows Update.
But this is the best part - you said it yourself, you hardly use Windows in the first place.
Edited 2012-12-04 13:42 UTC




Member since:
2007-08-22
It is just an other layer of extra code and (security) bugs.
Yes, virtual environments have their own issues.
However, they also mitigate many - not only do you need to penetrate the OS you're running in, you also have to penetrate the virtual environment and its hosts - which is made a lot more difficult when the host and guest OS's are not the same (as is my case).
So for me - you would have to penetrate Windows, VMware On Linux, and then the Linux OS; and if you wanted to do anything beyond what my Linux user could do, you'd have to do a root penetration as well - this all assuming I don't suspend/shutdown the guest OS while you're trying to do it.
There is also much less software installed in that environment that could lead to a penetration to start with.
Now you're assuming I need encryption within the virtual environment. While some may, I don't.
Even so, you can install hardware encryption technology into the VM if you needed it. So that is not really an issue. VMware, VirtualBox, QEMU, KVM, and others are also smart enough to use the underlying OS for things that require such functionality as well.
Agreed.
My primary purpose is software development and testing, not every day use. The most those systems use the Internet is for updating the tools using Windows Update.