2 ms·
I agree there is a privacy concern, however, if you took away that method in the package manager, you could still try invoking, say, standard methods in compone
by Zigurd 14y ago
I agree there is a privacy concern, however, if you took away that method in the package manager, you could still try invoking, say, standard methods in components in packages and guess their names.
The developers' domain names are public, so there is no way to prevent guessing parts of package names in Android and probably no way to prevent guessing complete package names.
Let's take a use case: I want to secretly check if you have banking apps installed. I can install them and discover their package names. Then I can make a malicious app that checks if some component of those apps exists, by checking for an intent filter match, for example. Then I present you with a targeted phishing attack that looks like those apps' screens. You didn't need to enumerate all installed packages to do that.
There are legitimate uses for enumerating all the packages. I've used it for a plug-in architecture for an app that enables 3rd party plug-ins.
- jseidl 14y agoZigurd, I get your point and I do agree that are diferrent ways on enumerating apps but you need to do some guessing. The evil part I think is that you can enumerate ALL apps without need to guessing. And I also agree with you that there are legitimate uses for that, as you have for sending/receiving sms, but my point is: Users should be warned that this app is attempting to do that so they can judge where to install it or no, as you have for all other sensitive information. I think all your points on both comments are good and valid and I'll update the post with that. Thanks for your opinions.