Yusuf makes good suggestions. My personal suggestion would be to include it in a class file of your java program, then obfuscate your code. If your attempting to prevent compilation this is your best bet.
On Apr 21, 5:32 pm, "Yusuf T. Mobile" <[email protected]> wrote: > From what I understand, your requirements are: > - your app uses data that it puts in a database during setup > - the end user should not be able to access this data, except through > your app's UI > > Possible cracks would then be Marco's decompilation idea, or > inspecting the database. Without knowing more about your app, I have a > few suggestions: > - bundle encrypted data with the app, but not the key to decrypt > - in the database, at least encrypt the names and values > - don't decrypt all the data at one time, only decrypt whatever the UI > requests > > One way to accomplish the last step is with a per-datum key fetched on > demand from your web service. However, depending on the value of your > data, hiding it and the key in your code may be sufficient to render > decryption not cost-effective. > > Yusuf Saib > Android > ·T· · ·Mobile· stick together > The views, opinions and statements in this email are those of the > author solely in their individual capacity, and do not necessarily > represent those of T-Mobile USA, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
