Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security notes on AppMessages #7

Open
iSoron opened this issue Jul 6, 2016 · 0 comments
Open

Security notes on AppMessages #7

iSoron opened this issue Jul 6, 2016 · 0 comments

Comments

@iSoron
Copy link

iSoron commented Jul 6, 2016

I am new to Pebble development, but going through the docs, there doesn't seem to be any notes about the security of messages sent from Pebble watchapps to Android apps and vice versa. In particular, the docs fail to mention that:

  1. Messages sent from the watchapp can be intercepted by any Android app, not only the app that they are "intended to". That is, if the watchapp transmits confidential data to the Android app, then the developer must take extra steps to obfuscate or encrypt such messages before sending them.
  2. A malicious Android app can easily create and send bogus messages to any watchapp, since UUIDs don't seem to be considered secret information. This could be done, for example, to crash a particular watchapp, to corrupt the user's data, or to force the watchapp to broadcast some confidential information. The watchapp developer, therefore, must take extra steps to guarantee that the messages received are coming from a trusted source.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant