You can certainly write a desktop application that will use any crypto algorithm you can find the source for (or find a JAR for). Writing "bare" desktop Java is so easy there's no need to be constrained by a particluar desktop tool set.
And somehow I find it hard to believe that javax.crypto would be irretrievably incompatible between the two versions. After all, it's necessary (and possible) for Android to be able to interchange with servers using encrypted data. More likely it's just a matter of getting both ends to use the same SPECIFIC algorithm, including not just the named algorithm (like DES) but also the nitty-gritty details of initialization vectors, "salting", and the like. On Oct 26, 1:31 pm, Vikas1976 <vikas.shah.1...@gmail.com> wrote: > Hi everyone, > > I am writing because I am writing an application that uses crypto to > encode information in files that will be stored and read on an Android > device, and I would like to develop a desktop SWT app to generate > these files. It seems that the JRE6 library and the Android 1.6 > library implement javax.crypto.cipher differently, and I end up with > error messages when I try to decode strings in SWT encrypted on the > Android device or vice versa. My question is whether you can force > Eclipse to use the Android's javax.crypto.cipher in the SWT app, or > use the JRE6 version in the Android app. > > Thanks! > > Vikas -- 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
