![]() One additional note: you can still detect if you're in a vm, by detecting clock drift. Telcos aren't foolproof, but WAY more secure than a home router! (And doesn't put your home network at risk.) If it had to have network access, I'd do it via cellular tether on the host. If I were to want to do this, I'd do it on a non-networked PC booted from a disposable Linux install (eg USB or live cd), no connected permanent storage, all wireless networks "forgotten" and all radios disabled, and in a vm with said mitigations. ![]() Three reasonably low probability events which nonetheless do and have coincided. That means that one if not multiple unpatched flaw(s) must exist, known about, and exploited. But I do know that even VMs can be broken out of, with the right exploits - typically involving a buffer overflow. I've never purposely infected a vm though, and am not a security expert. There are scripts you can download that change some of these properties for you. Google how to configure a vbox vm for hackintosh, for example. You should also change the advanved machine properties so that a virus can't detect the vm manager by inspecting standard ACPI etc properties. You also need to uninstall guest additions. It's not enough to just disable guest/host interop and disable networking.
0 Comments
Leave a Reply. |