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>
Fri, 29 Jan 2016 18:17:02 +0000 (10:17 -0800)
commitc2a36afd6772d9286e8071693f80648beef763a3
tree00347526394018525a69f65c4e0fca2965c45854
parent4a97cde443829f1a3bf40fe6e820ba5b01e3bf87
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

(cherry picked from commit de5bc04717505ad0e5b55605bccf43974f4c5c7a)

Change-Id: I4b100750e47788ab6ed897a0a5abfd33542e8676
core/definitions.mk
core/prebuilt_internal.mk
tools/releasetools/common.py
tools/releasetools/sign_target_files_apks.py