| commit | d4551e1eb319597c829d125546733b2e79fcb7cc | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Fri Jul 14 16:01:03 2023 +0100 |
| committer | Nikita Ioffe <ioffe@google.com> | Thu Jul 20 21:30:54 2023 +0100 |
| tree | a84d5b6c074fd37d9c038ac74c192a2530053b93 | |
| parent | 5886dc6db7198cb2f20cf9e6b1687750f4074fc7 [diff] |
Don't allow vendor APEXes in Microdroid A supported way for loading vendor code into Microdroid VMs is by providing a read-only dm-verity protected disk image (e.g. microdroid-vendor.img) as a separate virtio-blk device. Bug: 286390834 Test: add vendor apex to vm_config_apex.json of test apk & try to run VM Test: atest virtualizationmanager_device_test Change-Id: Ie6528a67185fffd52fabbb4123747f5bcb8bab67
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
How-Tos: