Peli,
My guess is that some kind of security layer will be added to the uses-
permission, etc. in the AndroidManifest.
- Juan
On Apr 2, 9:43 pm, Peli <[EMAIL PROTECTED]> wrote:
> Thank you for this information. I had not found it in the
> documentation.
>
> Regarding the security issue, both, Juan and you, suggest to perform
> whatever security checks are necessary for my needs. But let me ask
> again:
>
> I'm not worried about the intents that I have control about. I could
> program them securely, maybe even exchanging public encryption keys
> through the bundle.
>
> I'm more worried about intents available on the phone that have never
> been designed or have never been intended to be used through GTalk. As
> an example, there could be a 3rd party intent that takes a picture
> with the internal camera and sends it to a contact email address
> automatically. It might have been meant as an internal thing within
> another application that was never designed to work with GTalk, so no
> special security checks were necessary.
>
> But it seems to me that any person that is on my GTalk's friend's list
> can launch that intent on my phone, without any restrictions, and send
> random photos to their email address.
>
> This model suggests, that each IntentReceiver should check whether its
> bundle contains a "from" field, and if it does, it should be more
> careful about processing things.
>
> I (and I guess most developers) have written most intents so far
> without this check. Have I introduced security holes? Or is it really
> my (the programmer's) task to secure every intent against unwanted
> launches by GTalk messages, even if the intents are never designed to
> be launched by GTalk?
>
> Peli
>
> On Apr 2, 10:52 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > The intent does contain the sender of the intent. If you use
> > intent.getStringExtra("from") you will get the senders jid. If you
> > only want to process intent from a select group of people you will
> > need to add a check before processing it.
>
> > On Mar 31, 4:35 pm, Peli <[EMAIL PROTECTED]> wrote:
>
> > > I have the following conceptual question:
>
> > > If I look at the GTalkDataMessageReceiver example
> > > (http://code.google.com/android/samples/ApiDemos/src/com/google/androi...
> > > ) the receiver receives an intent that the sender sent. Except for the
> > > name "GTalk", there is nothing in that class that uses any GTalk
> > > related API. The intent could therefore either come from a local
> > > sender or from a remote sender.
>
> > > Of course, the sender has to be part of the buddy list of the receiver
> > > for this to work, but if this is the case, it seems the IntentReceiver
> > > will not obtain any information about who sent this intent (unless the
> > > sender is kind enough to put this information into the bundle).
>
> > > I have the following concerns:
> > > * Once I have rights to send intents to a phone, I could send
> > > arbitrary intents and trigger arbitrary events on anther person's
> > > phone.
> > > * The intent receivers do not know who sent the intent. If this
> > > information is passed in the bundle, a sender could pretend to be a
> > > different sender.
>
> > > There should probably be additional permission settings on the
> > > receiver's side which determine which intents can be received from
> > > which sender. So far, I don't see any permission that can handle this.
>
> > > Or am I missing something here?
>
> > > Peli- Hide quoted text -
>
> > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
