6 ms·
Is cosigning / joint signing not an option?
by dredmorbius 6y ago
Is cosigning / joint signing not an option?
- vesinisa 6y agoNot sure what you are referring to exactly, but Android on the phone only supports signing by one specific key. In the Play Store signing scheme, Google verifies the publisher by requiring that you sign the app first with a specific "upload key". Google then replaces (not co-signs) this with a key they control, and the handset verifies only against this Google-controlled key. For apps not enrolled in the Play Store signing scheme, the phone actually verifies directly against the publisher's key, that Google now wants to relegate just as an "upload key". I am saddened by Google's efforts to undermine this fundamental OS security feature. The ultimate goal is clearly to kill off any chance of competing app stores, as developers of new apps distributed through Play Store can now actually never access the key that's supposed to show they control the app, no matter what channel it was delivered through (e.g. Play Store vs. F-Droid.. Really bad for new Open Source apps!)
- Avamander 6y agoActually signature scheme V3 supports multiple keys.
- quotemstr 6y agoAny secure co-signing approach would require putting app developers in the loop. Are app developers going to do that? If developers want to provide device-optimized APKs, they can do that already without this Google-signs-the-APK stuff. [1] https://developer.android.com/google/play/filters https://developer.android.com/google/play/filters
- dredmorbius 6y agoDisclaimer: I know next to nothing about Android development. I do know a bit about PKI. And one option might be that the workflow be something like: Dev signs bundle => Google signs bundle (including dev signature) => User/Client verifies both signatures. Google are still signing here, but if the dev signature doesn't verify (or isn't present), there's a post-build modification occurring, which is the principle issue raised in the tweet thread.
- dbrgn 6y agoPost-build modifications are the whole point of App Bundles :) See https://developer.android.com/platform/technology/app-bundle/ https://developer.android.com/platform/technology/app-bundle... for details.
- UncleMeat 6y agoThe entire reason this exists is because of post-build modifications. A huge portion of an APK file is not useful on a given device. To save disk space and bandwidth and improve load times, Google will automatically remove content from APK files that aren't relevant for the particular device downloading the app. But doing this would break the signature unless Google possesses the signing keys.
- iggldiggl 6y agoOne the one hand yes, but on the other hand unfortunately it also complicates backups and makes them somewhat non-portable. While APK backups aren't officially supported and therefore might not factor into the decision making, curiously enough Google itself only recently added a feature to the Play Store which apparently allows direct sharing of APKs between nearby devices. Split APKs however mean that you can only sensibly share apps with devices having the same screen density, language, etc. as your own device, somewhat devaluating that feature again.