| commit | 8083582d084031424d959afb679a2114c9a5d4ac | [log] [tgz] |
|---|---|---|
| author | Michael Groover <mpgroover@google.com> | Tue Apr 26 15:17:14 2022 -0700 |
| committer | Michael Groover <mpgroover@google.com> | Tue Apr 26 15:17:14 2022 -0700 |
| tree | 6c20a33b3909f7b814b3e2fb1308e605d83c82ac | |
| parent | 45343b234b5c563e424177c66e6c6021edc7a013 [diff] |
Ensure v3.0 signer returned when app min SDK equals rotation min SDK Android T introduced the v3.1 signature scheme that allows apps to target APK signing key rotation to an SDK version T+ and the original signing key will be used for previous releases. Since releases under development use the SDK version of the previously released SDK, the v3.1 scheme also supports targeting a development release; in the case of T, the v3.1 block will target Sv2's SDK version (32) during development and the v3.0 block will use 32 as the max SDK version for the block. However, if an app's minSdkVersion is set to 32, the previous behavior would only return the v3.1 signer causing v3.0 signing to fail due to a missing signing config. This commit updates the logic to continue parsing the signers if the v3.1's minSdkVersion is equal to the app's minSdkVersion when supporting a development release. Bug: 230340743 Test: gradlew test Change-Id: Ibd13f899c7686cd5db6e509b6a2ecca73992b732
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.