Hi Aitor,

Well if it was an explicit Intent then in theory only your application can
be called via that Intent as you are referencing the specific component E.g.
Java Class to call. So other apps will not be able to "listen" on that
Intent. Note that I haven't assessed this myself, just going on the standard
documented behaviour.

There are other ways of an app sharing data, such as using URIs. Using a URI
will allow you to have a permission-based approach so that only the apps
with the correct, approved permissions can access your URI - and you can
distinguish between write and read permissions.

Without knowing a bit more about what your service is supposed to do and
what it is supposed to protect it is hard to say really.

--
Thomas.

On Mon, Aug 8, 2011 at 2:44 PM, Aitor Mendaza Ormaza
<[email protected]>wrote:

> Hi to everyone.
> First of all, sorry if this is not the correct place to ask my question.
>
> So, the question:
> I want to make an application that offers a "secure" service. I was
> thinking of offering an APK which will be listeing for a particular intent
> calling.
> My doubt: Is there any way to guarantee that no other application is
> listening to the same intent and catch the intent before my application
> does? Pretty much like a man-in-the-middle attack, or a Spoofing attack.
>
> Sorry if I don't explain myself clearly.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Android Security Discussions" group.
> To post to this group, send email to
> [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/android-security-discuss?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Android Security Discussions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/android-security-discuss?hl=en.

Reply via email to