apksigner: support codename Baklava

As part of the signing operation, apksigner will extract the min SDK
value from the unsigned APK's <uses-sdk android:minSdkVersion="..."/>
manifest entry. If the min SDK value is a string codename, apksigner
uses a hard-coded mapping of first letter of the development codename to
corresponding numerical value. Wrapping the codenames back from V to B
confuses the logic.

Add an explicit check for the codename "Baklava".

Note: the codename mapping seems to have been left unattended from
around the Android O time and the implementation of
getMinSdkVersionForCodename should be updated or rewritten (in a
separate CL).

Test: m
Bug: 354023031
Flag: EXEMPT introducing new version codes can not be flagged
Change-Id: Icfedc4df24ab7945a02b7f6727fb2ef6a772b737
1 file changed
tree: 4e13eea66e75735dfeefb1b89523580a16a1d01a
  1. etc/
  2. gradle/
  3. src/
  4. .gitignore
  5. Android.bp
  6. android_plugin_for_gradle.gradle
  7. build.gradle
  8. gradlew
  9. gradlew.bat
  10. LICENSE
  11. OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

apksig

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 -- a pure Java library, and
  • apksigner -- a pure Java command-line tool based on the apksig library.

apksig library

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

apksigner command-line tool offers two operations:

  • sign the provided APK so that it verifies on all Android platforms supported by the APK. Run apksigner sign for usage information.
  • check whether the provided APK's signatures are expected to verify on all Android platforms supported by the APK. Run 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.