You can usually read non forward locked apk's out of /data/app if you know what their exact path names should be, even though you can't browse. However, I'm not sure that will always be bit for bit the same as what you distribute (for example I forgot to zipalign something the other day, and logcat seemed to indicate the phone was doing it).
Anti-piracy measures often rest in the gap between what a third party has access to, and the degree to which they understand in detail what they are looking at. However it would seem that if you have a server involved you have other options. Either sell the app directly and keep track of purchasers, or use market licensing and have the app forward the license server's response to your server when it requests something from you. William Ferguson wrote: > I would love your solution to work, but surely any pirate will be able > to calculate exactly the same checksum. > If they have access to your apk, they have access to the key or > algorithm you are using. > > On Sep 20, 8:07 am, Bret Foreman <[email protected]> wrote: > > As an additional anti-pirating strategy, I'd like to compute a > > checksum on my application at runtime. Since my app communicates with > > a back-end server, I can send the checksum with each message and the > > server can deny service to altered apps. Not a complete solution to > > piracy by any means, but a fairly easy way to raise the bar. > > > > Anyone know how an app can get access to it's load image at runtime? -- 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] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
