Re:Android Developers Blog: Exercising Our Remote Applicatio...
by fierarul on Friday June 25, 2010 @03:09PM
(#1461777)
Well, it was just an example and
>If you make sensitive data public, it becomes public data, period; there's no going back.
this is true, but it sure would be nice to do damage control no ?
Even if Google initiates a mass revocation, that doesn't mean the application is no longer in the wild. Users who want to exploit your mistake could just as easily do one ogf the following:
- Disconnect their phone from a data connection or wifi signal
- Dump their current ROM/data to a backup image using a 3rd party bootloader
- Extract the .apk from the phone using root access, using an app like Titanium Backup
- Install the .apk from a source other than the Market, so that the revocation system will ignore it
Google's mass-revocation system only "works" because it is designed to remove malicious applications from the phones of unsuspecting users. If you make sensitive data public, it becomes public data, period; there's no going back.