I am considering adding a means by which my app can perform functions over Google Voice, and the functionality would make little sense if I required the user to type in a password.
I'd like a reasonable plan for storing the password locally and sending it (through google-voice-java) when demanded by Google Voice. Clearly, I'd like to properly represent the risks of the chosen scheme honestly to the user. I'd like the storage to be based atop writing it into a SharedPreferences created with flags=0 What form of obfuscation is suitable, and with what available salting ingredients and such should I customize it? tone -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
