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>
Tue, 26 Jan 2016 18:41:57 +0000 (18:41 +0000)
commit74df828cb574a6f30be9b9dcf286773ca1835f72
treeec44143997f7ce98b3c110068a617e59fa5e47b3
parent385ac86745e2294e3ac8da7540659a2150ac7923
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: I058393e0971d0d6559dbd69ea902754c6c7cab14
(cherry picked from commit de5bc04717505ad0e5b55605bccf43974f4c5c7a)
core/definitions.mk
core/prebuilt_internal.mk
tools/releasetools/common.py
tools/releasetools/sign_target_files_apks.py