On Tue, Mar 26, 2013 at 4:28 PM, Jeffrey Walton <[email protected]> wrote: > On Tue, Mar 26, 2013 at 4:03 PM, Kristopher Micinski > <[email protected]> wrote: >> Right, so I guess I'm still not understanding your question: are you >> just trying to ask what the best static analysis technology is to >> fight against this. > No, I can find the problems in the code during review. > >> or something else? > Yes. Suppose my application rotates. That means its going to be killed > and then restarted. How do I pass that cached password between > instances of my program so the user is not prompted to > re-authenticate? In general, how do I securely transition between > states? >
I guess I'm confused here because you application is not killed, your *Activity* is killed. You will still have the same application context (at least, if things haven't changed from what I read a year or two ago..). Kris -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/android-security-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
