| commit | 185e34cdfe20645a4cf84b72142d15a2dad4f47f | [log] [tgz] |
|---|---|---|
| author | Alan Stokes <alanstokes@google.com> | Fri Nov 24 12:28:39 2023 +0000 |
| committer | Alan Stokes <alanstokes@google.com> | Tue Nov 28 15:54:26 2023 +0000 |
| tree | 059b02e447b56616b57b50e6d59f02cb61a12228 | |
| parent | a5fc4d4acab1ed16e62a30371019a596abc50c5a [diff] |
Get apexd to verify manifest data Send the name and version we read from the manifest to apexd to make sure it doesn't change. Remove image hash since we have no use for it. Put the manifest extraction & verification behind a flag since it now has the potential to change behavior. Expand on the comment for verify(), to make it clearer what it does and doesn't verify. Bug: 313042092 Test: atest ApexTestCases Test: atest MicrodroidTests Test: atest libapexutil_rust.test Change-Id: Ida6d9e11b3bce5676b744dc945eadb09aa9a822f
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: