2 ms·
For the first case, I'd rather use something like Google Native Client. The attack surface of a VM is rather large, particularly when you consider the dozens o
by rwmj 14y ago
For the first case, I'd rather use something like Google Native Client.
The attack surface of a VM is rather large, particularly when you consider the dozens of emulated devices and instructions. For example, there was a notable hole in SCSI emulation recently discovered which let any guest overwrite any part of a host's disk (by sending some obscure SCSI commands which weren't being filtered by the virtualized device properly).
- e12e 14y ago> For the first case, I'd rather use something like Google Native Client. Wait, you're saying Google NaCl could be going the way of Java -- being used for server side containers, rather than client side apps? (I don't really see why you'd want that over using a single process(tree)/binary compiled from go...).
- e12e 14y agoOh, I see. Zerovm[1,2] is built on top of NaCl, and does indeed appear to be a "javaosification" of NaCl -- with no bytecode, no dedicated language, but a sandbox/lockdown of native code. [1] https://news.ycombinator.com/item?id=3746222 https://news.ycombinator.com/item?id=3746222 [2] http://zerovm.org http://zerovm.org