diff options
| author | Bryan Henry <bryanhenry@google.com> | 2018-07-26 22:30:28 -0700 |
|---|---|---|
| committer | android-build-team Robot <android-build-team-robot@google.com> | 2019-06-20 01:34:46 +0000 |
| commit | fa00d60b1239b7f7830b2b818ef15993e4ebc217 (patch) | |
| tree | 1bdde61fa96faf466e40f78c3d6580c8f54c6dd9 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | d29c48e3c3165bd7ee50109a7ed633290caf429a (diff) | |
Collect APK certificates after an OTA, rather than relying on timestamps
Checking APK file modified timestamps is not a reliable signal to
determine that the APK signature may have changed. APKs in the system
image (anything that passes through add_img_to_target_files) have all
file timestamps rewritten to 2009-01-01, for instance, so timestamp will
explicitly fail to detect changes in the platform key across an OTA.
Bug: 80093599
Bug: 74501739
Test: Verified OTA between test-keys and dev-keys worked for 2 builds
with same APK timestamps, and signature changes were picked up.
Change-Id: Id3e5afbfe22e63d70cd176f1e438e2fa143ccd65
(cherry picked from commit 770f3579dcc5a1697e0e5c3474e8fa34fd21d3dd)
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions