| commit | 45f34cf07116cf9b13809bd0d24f37670558c0b9 | [log] [tgz] |
|---|---|---|
| author | Michael Groover <mpgroover@google.com> | Thu Nov 11 13:51:57 2021 -0800 |
| committer | Michael Groover <mpgroover@google.com> | Thu Nov 11 13:51:57 2021 -0800 |
| tree | dbeac2eb266b3897b31ed50998493ea0541dbf61 | |
| parent | 72fd03affc104d64f3131f19cada85eaff4bff76 [diff] |
Update minSdkVersion for v3.1 block to Sv2 API level (32) During the development of a new platform, the SDK version of the most recently finalized platform release is used. Initially T used the SDK version of S (31), but recently Sv2 was finalized and the SDK version was bumped to 32. In order for the v3.1 signing block to be recognized on a device running T, the device SDK version must fall within the bounds of the v3.1 signer's min / max SDK version. The v3.1 signature scheme will still work on devices running T with the new SDK version of 32 since apksig was using 31 as the min SDK version, but this value is also used as the max SDK version for the v3.0 signer. Since Sv2 is also using 32 as its API level, the max SDK version of 31 written to the v3.0 signer block prevents the device from recognizing a proper v3.0 signer. This commit updates the API level used for the v3.1 signer block to 32 which will also update the v3.0 signing block to use 32 as the max SDK version allowing APKs signed with the v3.1 signature scheme targeting T for rotation to properly install with the original signer on a device running Sv2 with the finalized SDK. Fixes: 205551461 Test: gradlew test Change-Id: I44d65c36adfea4d792ae97afa1aac6ddfd09bdd3
apksig is a project which aims to simplify APK signing and checking whether APK signatures are expected to verify on Android. apksig supports JAR signing (used by Android since day one) and APK Signature Scheme v2 (supported since Android Nougat, API Level 24). apksig is meant to be used outside of Android devices.
The key feature of apksig is that it knows about differences in APK signature verification logic between different versions of the Android platform. apksig thus thoroughly checks whether an APK's signature is expected to verify on all Android platform versions supported by the APK. When signing an APK, apksig chooses the most appropriate cryptographic algorithms based on the Android platform versions supported by the APK being signed.
The project consists of two subprojects:
apksig library offers three primitives:
ApkSigner which signs the provided APK so that it verifies on all Android platform versions supported by the APK. The range of platform versions can be customized.ApkVerifier which checks whether the provided APK is expected to verify on all Android platform versions supported by the APK. The range of platform versions can be customized.(Default)ApkSignerEngine which abstracts away signing APKs from parsing and building APKs. This is useful in optimized APK building pipelines, such as in Android Plugin for Gradle, which need to perform signing while building an APK, instead of after. For simpler use cases where the APK to be signed is available upfront, the ApkSigner above is easier to use.NOTE: Some public classes of the library are in packages having the word “internal” in their name. These are not public API of the library. Do not use *.internal.* classes directly because these classes may change any time without regard to existing clients outside of apksig and apksigner.
apksigner command-line tool offers two operations:
apksigner sign for usage information.apksigner verify for usage information.The tool determines the range of Android platform versions (API Levels) supported by the APK by inspecting the APK's AndroidManifest.xml. This behavior can be overridden by specifying the range of platform versions on the command-line.