| commit | 9a7b007cbd9f1e0fce396010e48a353271a456a4 | [log] [tgz] |
|---|---|---|
| author | Alan Stokes <alanstokes@google.com> | Mon Jan 22 15:49:21 2024 +0000 |
| committer | Alan Stokes <alanstokes@google.com> | Mon Jan 22 15:49:21 2024 +0000 |
| tree | 2acdf8b606126434af42229750a33cb13bbf9e1f | |
| parent | 1b670a4a98c6c6140887ca2bd58b7de2182fdb11 [diff] |
Treat APK path change as compatible The path to an APK may change, on an update, or at any other time when it's not running. So we shouldn't treat a path change as rendering the VM config incompatible. (If the new path points to an APK with a different signature or incompatible version then starting the VM may still fail - but we can't determine that statically from the config, any more than we can from checking package names.) Modify the relevant test to match. Bug: 321184334 Test: atest MicrodroidTests Change-Id: I384360b0d19013b12da338af95cbc5ae104fa983
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: