We use SMS interception for system signalling. Is there a mechanism for an app to respond and stop the signaling chain? Is there security around that so that one vendor can’t hijack a message and respond to it?
- 1 Answers
- 1983 Views
- I also Faced
- E-Mail Answers
Answer / mady
There’s a mechanism where an application can register to receive a message with a certain signature and prevent others from getting it. We have a system of permissions apps are able to declare, enforce, and require to perform certain operations. Things like dial the phone, get to contacts, etc.. But these aren’t things that are baked in the core of the system. An arbitrary app could declare custom permissions.
As far as restricting another app, the model we’ve been going by... the phone is not controlled by the application vendor, it’s controlled by the user. Whether or not the permissions are granted is up to the user that owns the phone. If you created a protocol that intercepts an SMS and another party wrote an app that intercepts the same SMS and the user wants to use that, the user could be free to stick that in.
| Is This Answer Correct ? | 2 Yes | 0 No |
What is an activity?
What’s wake locks?
What is android on cell phones?
How much dialog boxes are supported in android?
Is android 5 outdated?
What is a service?
Tell us what is the relationship between the life cycle of an asynctask and an activity? What problems can this result in? How can these problems be avoided?
What is android:targetsdkversion?
How can anr be prevented?
What is api level, codename of android 4.1 – 4.3?
Which are the dialog boxes supported by android platform?
What language does Android support for application development?
Apple iOS 
