OSDN Git Service

Sign APKs using SHA-256 instead of SHA-1 when possible.
authorAlex Klyubin <klyubin@google.com>
Wed, 13 Jan 2016 18:32:47 +0000 (10:32 -0800)
committerAlex Klyubin <klyubin@google.com>
Thu, 21 Jan 2016 18:25:12 +0000 (10:25 -0800)
commitde5bc04717505ad0e5b55605bccf43974f4c5c7a
tree0047ef4f88d0df18c825414ba584d70310dd919c
parent3cc36050109fa1f310f11fca980ac415cb58bee7
Sign APKs using SHA-256 instead of SHA-1 when possible.

This changes the build system to provide the signapk tool with the
minSdkVersion of the APK being signed. signapk in turn will then use
SHA-256 instead of SHA-1 if minSdkVersion is 18 (JB MR2) or higher
(see c2c49ed0c13846f7f96249c7419971dfcddc9215).

To avoid increasing incremental OTA update package sizes for already
released platforms, release build scripts disable the above logic when
signing target files ZIPs for pre-N platforms.

Bug: 25643280
Change-Id: I048393e0971d0d6559dbd69ea902754c6c7cab14
core/definitions.mk
core/prebuilt_internal.mk
tools/releasetools/common.py
tools/releasetools/sign_target_files_apks.py