| commit | de40e641be35687fb94fbb47a06468b8b8d80e46 | [log] [tgz] |
|---|---|---|
| author | Alan Stokes <alanstokes@google.com> | Tue Jun 04 13:36:05 2024 +0100 |
| committer | Alan Stokes <alanstokes@google.com> | Tue Jun 04 14:44:22 2024 +0100 |
| tree | e9f52369d00fb74e006ff7cbf49b007b8cf5c761 | |
| parent | 55e57b98cdb27d292b80a07a5881a8b46f0ee8c4 [diff] |
Only delete owned VM IDs When a VM is deleted, only delete its secret from Secretkeeper (and our tracking DB) if we believe it is owned by the caller. This is intended to handle the VM transfer case - on transfer we mark the recipient as owner, and we want them to retain access until they delete the VM. The previous owner is encouraged to delete their copy immediately, which shouldn't invalidate the secret. Modify our e2e test for VM transfer to do the deletion after transfer and before starting the VM, so we are exercising the expected use case. This test then fails, as expected, without the code chage and passed with it. Bug: 340563554 Test: atest com.android.microdroid.test.MicrodroidTests#testShareVmWithAnotherApp Change-Id: I1929a1a3e2f92343629f15893a3a68f51d244afc
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: