Re:Saving Data: Reducing the Size of App Updates by 65%
by orf on Wednesday December 07, 2016 @04:04AM
(#13121357)
Because then to check the signature you'd have to decompress the app. Android runs on lots of hardware, much of which is not very powerful. I would imagine this is also why they use deflate, perhaps others achieve x% better compression if it'd a lot slower on certain hardware then maybe it's not worth it.
[ Parent
| on HN ]
Re:Saving Data: Reducing the Size of App Updates by 65%
by pja on Wednesday December 07, 2016 @06:16AM
(#13121767)
Two signatures: one on the compressed APK which is used on the initial install & one for the concatenation of the uncompressed data which is used to check in-place upgrades.
Obviously the diffs themselves also need to be signed in some way to prevent bad actors injecting data into the decompression system, but that’s a separate issue to checking that the updated App matches the data originally delivered to Google by the App developer.