Linked by David Adams on Thu 24th Jun 2010 16:22 UTC, submitted by Governa
Thread beginning with comment 431361
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by anevilyak
by jtfolden on Thu 24th Jun 2010 20:20
in reply to "RE[2]: Comment by anevilyak"
Well, that's sort of what I was getting at... how the user is alerted. For example, some sort of address book related app might, logically, ask for the permissions to make calls when first installed. Isn't this a situation where if it were a malicious app it could then later, make calls/send texts without notice?
RE[4]: Comment by anevilyak
by anevilyak on Thu 24th Jun 2010 20:38
in reply to "RE[3]: Comment by anevilyak"
Well, that's sort of what I was getting at... how the user is alerted. For example, some sort of address book related app might, logically, ask for the permissions to make calls when first installed. Isn't this a situation where if it were a malicious app it could then later, make calls/send texts without notice?
That's certainly the case. What it does help you catch though is cases where an app is asking for rights it very obviously shouldn't need. For instance, suppose you go to install a game, and it asks for the right to make calls. Why would it possibly need that? That's the case it's designed to catch. An app later making malicious use of the capabilities you've allowed it to have is another animal entirely, and I don't see an easy way around that short of prompting every single time the app tries to do anything whatsoever, which would be a cure worse than the disease.





Member since:
2005-09-14
If I understand your question correctly, the rights it asks for at install time are all it ever gets. Ergo, if it didn't ask for the "make calls" right when you go to install it, it cannot suddenly change its mind later and will fail if it tries to.