| commit | 8f7db050c041ae4851df9d93d96b1b892c5ad9a7 | [log] [tgz] |
|---|---|---|
| author | Alan Stokes <alanstokes@google.com> | Thu May 09 10:13:28 2024 +0100 |
| committer | Alan Stokes <alanstokes@google.com> | Thu May 09 14:11:36 2024 +0100 |
| tree | aeb243623984579156d12d0b3615046b37071a3d | |
| parent | b2f52fbb36161bde0cfa3661765acbad0221174b [diff] |
More lenient config descriptor parsing Some DICE nodes simply have a hash in the config descriptor field; so if parsing as the expected CBOR fails, we should ignore that. Some nodes also have no name field, so we need to cope with that too. And the SubComponents key in the config descriptor map is not reserved, so it may appear in any DICE node with arbitrary content. So we defer parsing the subcomponents until we've figured out which node describes the Microdroid payload. Bug: 338745127 Test: atest VmAttestationTestApp Change-Id: I70169fc77170e2286d93246b079d3036d544b776
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: