On Mon, Feb 6, 2012 at 6:12 PM, Kosmo Kosmorum <elko...@gmail.com> wrote: > Thanks for your replay. > > We try to run this app on a Android 2.2, because it is the minimum > target we need to handle, so we don't know if this solution works with > other type of clients.
If you want maximum compatibility, just use RSA. > > In my previous message I said that there was a link where we can read > that there is a way to have EC working on a 2.2 device, but not > applied to a HTTPS connection , only related to cyphering > functionality. I wrote that blog post :) You can install an additional JCE provider and use ECC (or any algorithm supported by the provider), even if it is not supported by the platform. However, > Do you think this is not supported directly by https? > Android's SSL sockets are implemented using native OpenSSL code, and thus JCE providers are not used. I haven't checked in detail, but most probably you can't get it to use ECC for SSL without modifying the platform. In short, just use RSA. If you really, really need to use EC, get someone to look at the source, and possibly modify the platform. -- 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