On Jul 6, 2011, at 12:30 PM, Brian Carlstrom wrote: > In this case you should have no road blocker using > android.security.KeyStore - you are saving and retrieving with the > same user id. > > Except that its not a public API and can be changed (or removed) without > notice. > > -bri
Right, understood. The main issue with using the KeyStore API is, like I said, the PSK is encoded with the uid of the current process. We would store it from our app using the user uid, but when we initiate the connection, the system's VpnService would go to read it under the system uid, and that's where it would fail. I'm trying to determine if there is an alternate method for specifying the PSK, but it's sounding like there is none. Thanks, Jeff -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" 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-security-discuss?hl=en.
