That's sort of what I was under the assumption of. Either segregate the local code that would be shared with the public on an external server or risk it being reverse-engineered. Only steps to obscure data can be put in the place to dissuade an attacker but not prevent them.
> And you mentioned in a previous post that the Android library was > obfuscated. Why do you believe this? Android is open source, you can > find the sources to android-x.jar easily online. > > kris Not the Android API. The Google API, such as Google Maps API, etc. I had recalled that those libraries were not publicly shared, but I could be wrong. -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To post to this group, send email to android-security-discuss@googlegroups.com. To unsubscribe from this group, send email to android-security-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/android-security-discuss?hl=en.
