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>
Wed, 10 Feb 2016 17:40:31 +0000 (09:40 -0800)
commit2cfd1d108c82bdedccb03917e09aa5e677e8fde2
tree22d5d0a156646e9bf9e1b53f7f0b7a5738dea52e
parent8290ba9e0df3e6f4ef8c21e3964862f90944ead2
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: I3f2faaf49c6fa392ffbf1ee9f30de476f9f73231
core/definitions.mk
core/prebuilt_internal.mk
tools/releasetools/common.py
tools/releasetools/sign_target_files_apks.py