tag | f6ef778ddc5fc879ec2a226ba3b73af2f6fd9b03 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Oct 27 09:35:38 2021 -0700 |
object | 54838dc65ba67525df9eada64eb6f953008c97bd |
Android S V2 Preview 1
commit | 54838dc65ba67525df9eada64eb6f953008c97bd | [log] [tgz] |
---|---|---|
author | Victor Hsieh <victorhsieh@google.com> | Fri Oct 08 17:46:36 2021 -0700 |
committer | Victor Hsieh <victorhsieh@google.com> | Fri Oct 08 17:50:22 2021 -0700 |
tree | 69cd677e20d63a09e45dae529827c64d7ca1aee4 | |
parent | 30104206f27c22f6da69013b20cdb8f49448e2c0 [diff] |
Generate hashtree for com.android.i18n.apex Although the APEX is always shipped in the system image, which already has dm-verity protected, we need to access to APEX from outside of Android in a Protected VM. The VM, which doesn't trust Android, needs to mount the APEX image and use dm-verity to verify the content. Bug: 200210074 Test: m Change-Id: I1b2cb2658984174653ec093754d9db9ed25f4a91