5 ms·
> Or maybe this is just for old DOS/Win games that'll sell for $9.99 in the appstore. Maybe it's the start of an "extreme sandbox" model, where appstore apps
by toyg 12y ago
> Or maybe this is just for old DOS/Win games that'll sell for $9.99 in the appstore.
Maybe it's the start of an "extreme sandbox" model, where appstore apps are all virtualized.
- X-Istence 12y agoThis is something I've been thinking about. What if we could easily allow all programs to be sandboxed using virtualisation technology? Run your web browser or parts thereof inside of a VM so that any exploits are limited to just that VM.
- transpute 12y agoBromium does this for common apps (web, pdf, office) on Windows, e.g. each browser tab and HTTP request is a separate VM.
- NickNameNick 12y agoIt also alerts if a process does something 'weird', it allows exploits to run in a sandbox and records what they do, so you can analyse it later.
- blinkingled 12y agoThat's way more heavy weight compared to regular seccomp like sandboxes that Chrome uses on Linux - and for too little gain.
- mschuster91 12y agoThe question is, what exactly is the overhead of VT-d and friends, especially when done at OS-level (every process gets its own "virtual" cpu?)
- 0x0 12y agoWell, you would need to install 20 copies of OSX if you have 20 apps installed, for one. Also, for a regular app process, standard unix-level memory protection plus sandboxing should be enough. Regular apps have no use for the virtual ring0 privileges available in a "bare-metal" environment that such virtualization emulates.
- mschuster91 12y ago> Well, you would need to install 20 copies of OSX if you have 20 apps installed, for one. Shouldn't it be possible to use bindmounts or other virtual filesystems for the core services?
- wmf 12y agoSure, that's like novm (https://github.com/google/novm https://github.com/google/novm). But you're still running 20 kernels. A picoprocess architecture is better, but I'd still go with containers.
- mschuster91 12y ago20 kernels... well, not every kernel needs to be a full kernel. Maybe tiny microkernels?
- 0x0 12y agoBut, you'd need a complete implementation of the OSX kernel and library API surface, because that's what an OSX app expects. If you're going to try to re-use the host kernel via a virtualCPU backdoor, you're not really virtualizing anything anymore and could just stick with the unix process model?
- mschuster91 12y agoNot exactly, because using a separate CPU with a shared kernel can very effectively isolate processes from each other which is not possible with the unix process model. It would take either a serious kernel bug or a bug in the CPU hardware/microcode to cross the barrier in case of an exploit e.g. in a browser.