2 ms·
> It tries to provide an environment suitable for a legacy application model that doesn't really take security as seriously. Erm... what? > The only real way
by AshamedCaptain 2y ago
> It tries to provide an environment suitable for a legacy application model that doesn't really take security as seriously.
Erm... what?
> The only real way to win here is by using a VM which is what ChromeOS did.
What advantage would the VM provide, other than the host OS having even less insight into what the application is doing?
(Which is, by the way, exactly the only reason Android is introducing VMs: hiding stuff from the host Android)
- fragmede 2y agoThat's not the reason. The host android has full access to the child VMs; the VM can't hide anything from the hypervisor. It's about isolation. The child VM can't leak your photos or contact list if it doesn't have it in the first place, and sticking things into their own VM provides an additional layer of isolation beyond what exists currently.
- yjftsjthsd-h 2y agoI don't think that's true; my recollection, which appears to match https://source.android.com/docs/core/virtualization/architecture#hypervisor https://source.android.com/docs/core/virtualization/architec... , is that Android uses hardware support to run VMs that even the host kernel can't actually see into.
- fragmede 2y agofascinating link, thank you! The host android won't have access to the guest VMs but the hypervisor still does.