| commit | f6e52e68c0f97dfddbba69f7b96524b93b8dce9f | [log] [tgz] |
|---|---|---|
| author | Alan Stokes <alanstokes@google.com> | Mon Nov 06 15:04:32 2023 +0000 |
| committer | Alan Stokes <alanstokes@google.com> | Mon Nov 06 15:04:32 2023 +0000 |
| tree | c6a6cd1153687b42c17c010beab8840f4db9fa59 | |
| parent | 2acf573762004d07ceb49a5bdbc2ab0266059524 [diff] |
Minor init.rc tweaks I don't think the owner/group of the directories we mount APKs in matters much, but we should at least be consistent. We don't really use the system user, microdroid_manager runs as root, so let's use that. We don't need the explicit restorecon since init's mkdir does one automatically. (And does it before we start microdroid_manager, avoiding a race condition - admittedly a very unlikely one.) Bug: 308759880 Test: Started a VM with & without extra APKs Change-Id: I3266ce626405e933fd82c8cd4dd064e0a9a223b9
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:
AVF APIs:
How-Tos: