| commit | 976035677ce41fb11a471d84fd5f5a2f8b4d386e | [log] [tgz] |
|---|---|---|
| author | Seungjae Yoo <seungjaeyoo@google.com> | Thu Feb 22 15:34:08 2024 +0900 |
| committer | Seungjae Yoo <seungjaeyoo@google.com> | Fri Feb 23 11:58:15 2024 +0900 |
| tree | a7d5b09875d02adeb673245540aed5e685f36003 | |
| parent | 9001b9afbf1bc41f03e2bedf99140db02d00b838 [diff] |
Resign microdroid_vendor.img with avb_vendor_key microdroid_vendor.img is vendor image for running Microdroid, a type of VM run on top of Android. microdroid_vendor.img is currently stored in host device's vendor partition. However the original key signed for microdroid_vendor.img is not enrolled in the signing server, so it can make possible test breakage if there's a test checking all files in the partition is signed with trusted key. Therefore, this is the patch to resign micrdoroid_vendor.img with avb_vendor_key. When vendor image of host device is resigned with that key, microdroid_vendor.img would be resigned as well with the same key. Bug: 285855442 Test: First, for testing, modify the script to skip all files except VENDOR/etc/avf/microdroid/microdroid_vendor.img in ProcessTargetFiles. Second, run following commands and check if script doesn't throw any error until ProcessTargetFiles ends. - sign_target_files_apks --avb_vendor_key external/avb/test/data/testkey_rsa2048.pem --avb_vendor_algorithm SHA256_RSA2048 <source_zip_file> <target_zip_file> - sign_target_files_apks --avb_vendor_key external/avb/test/data/testkey_rsa4096.pem --avb_vendor_algorithm SHA256_RSA4096 <source_zip_file> <target_zip_file> - sign_target_files_apks --avb_vendor_key external/avb/test/data/testkey_rsa8192.pem --avb_vendor_algorithm SHA256_RSA8192 <source_zip_file> <target_zip_file> Third, `unzip <target_zip_file>` and do `avbtool info_image` Change-Id: I5337f61ab9eca7e6d0f92860486bc820b6e09eac
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.