History log of /build/tools/releasetools/check_target_files_signatures
Revision Date Author Comments
a5f534df07a598f3fc9d353a1a9a0ff6c09cfbc0 11-Nov-2011 Doug Zongker <dougz@android.com> use frozensets to represent APK cert sets

Change-Id: Ic92c83be0c3f6a76bf1bd21f0216cd1b87586959
278c9781ec5d2ef289fee635dfcfd8befcfe531b 09-Nov-2011 Doug Zongker <dougz@android.com> to be upgraded, APKs must have exactly the same set of certs

Change-Id: I0d528d3d55e5ee553e57e63ed1f998172c6306f8
b40a58e4b3cdb6dd528c9b3f23890ef008732a89 29-Sep-2011 Doug Zongker <dougz@android.com> allow APKs to be signed with multiple certs

The Package Manager handles this now. To share a UID, all packages
must be signed with exactly the same set of certs.

Change-Id: I2fd08923f55f02ae2f1d503266ab124be2472921
cad0bb9f621ff1ccfb584e18249b09768c30a0c0 15-Mar-2011 david <zathrasorama@gmail.com> sha module is deprecated

This patch removes the deprecated warnings from the python
scripts.

Change-Id: I052a0aab3fb28dd1d78de1307edafda6b6c35e5f
6ae5381670a12f63b4f7a18166e0886898e2083b 27-Jan-2011 Doug Zongker <dougz@android.com> fix check_target_files_signatures

common.UnzipTemp now returns a 2-tuple instead of just a string.

Bug: 3398407
Change-Id: Ifd0408283aaa15752caa549f4510a0a3db03c3fd
27bb6f5f234332d161a050b32717d94b38e63823 08-Dec-2009 Doug Zongker <dougz@android.com> add signing checker script to releasetools

The check_target_files_signatures determines what key was used to sign
every .apk in a given target_files. It can compare that signature to
that of another target_files (eg, the previous release for that
device) and flag any problems such as .apks signed with a different
key.

(This is a backport of a change in froyo. It does not affect device
code, only the scripts that sign images and OTA packages.)
f6a53aa5f24878ad9098409ed3d3f41bb5c63fb5 16-Dec-2009 Doug Zongker <dougz@android.com> add "EXTERNAL" as special value of LOCAL_CERTIFICATE

Setting LOCAL_CERTIFICATE to "EXTERNAL" now marks an apk (either a
prebuilt or otherwise) as needing the default test key within the
system, but one that should be signed after the target_files is
produced but before sign_target_files_apks does the rest of the
signing. (We use this to ship apps on the system that are signed by
third parties, like Facebook.)
75f1736469d6ebfb51f7d2abfa74039d9be54d8d 08-Dec-2009 Doug Zongker <dougz@android.com> add signing checker script to releasetools

The check_target_files_signatures determines what key was used to sign
every .apk in a given target_files. It can compare that signature to
that of another target_files (eg, the previous release for that
device) and flag any problems such as .apks signed with a different
key.