4 ms·
> But despite best efforts by the community to verify builds, Google and Apple can be forced to upload a malicious app to a particular user, meaning they aren't
by greysonp 6y ago
> But despite best efforts by the community to verify builds, Google and Apple can be forced to upload a malicious app to a particular user, meaning they aren't using the same app at all.
Hi there! Signal-Android developer here. App signing verification is done at the OS-level, and Google does not have our signing key, so they wouldn't be able to give an existing user a different APK and have it successfully install.
- ndiscussion 6y agoIs that really true? Couldn't Google forcibly turn off the code-signing requirement on an individual's phone? They've been known to reset passwords remotely in the past: https://www.theverge.com/2016/3/30/11330892/fbi-google-android-unlocking-phone-court-order https://www.theverge.com/2016/3/30/11330892/fbi-google-andro...
- codethief 6y agoNo, they could not. And if you don't want to trust $random_manufacturer's Android ROM, you could switch to GrapheneOS[0] whose developer Daniel Micay attaches a lot of importance to reliable app signatures (which is why GrapheneOS doesn't come with MicroG as the latter would need signature spoofing). [0]: https://grapheneos.org/ https://grapheneos.org/