| commit | 06de09066f1cd77df4e0f384d6ffa5ca3f571298 | [log] [tgz] |
|---|---|---|
| author | Gil Cukierman <cukie@google.com> | Wed Mar 19 11:28:53 2025 -0400 |
| committer | Gil Cukierman <cukie@google.com> | Wed Mar 19 13:54:01 2025 -0400 |
| tree | 4c1bc05d52d9be4a7ab92d1014e483068919a04a | |
| parent | 87baaef7c86f0b1ddef3f78045e0ce22eaa9dbc8 [diff] |
trusty: Add unique component names to each vm
Since trusty system vms are signed with the same key, component names
help us build VM-specific dice policies. The com.android.virt.name
property is used as the component_name in the dice leaf derived for
each vm payload.
Bug: 401286789
Test: m trusty_test_vm_signed_bin
Test: Manually validate footer with avbtool info_image --image {path_to_bin}
Change-Id: I19339d13c1d54a573a6272326e06d9a37de61c84
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: