What ever Security patterns we implement in SOA type architecture, the key data transfer is done via XML or something similar, which are easy to understand and moreover no decoding is required. What you think of this problem?? Any solution??
Actualy i was not concerned about this security issue earlier, thats why i am asking.....
Originally posted by Lester D Jones: What would you consider the key issues in security for J2ME applications?
I have been using Bouncy Castle for a while and I am satisfied with the results. Are there any other APIs worth looking into?
thanks for the contribution to the community
In our book, we do address the security issues and requirements related to J2ME devices...and explain them in terms of using - securing MIDlets, Trusted MIDlets and then how to use cryptography in J2ME. In the J2EE security architecture, we also discuss on how to use secure J2ME clients using MIDP 2.0 for invoking J2EE applications (using WTLS).
BouncyCastle does work well in light-weight environments including J2ME. I don't want to distinguish differences and give my biased opinions. [ January 11, 2006: Message edited by: Ramesh Nagappan ]