OK, and thanks for your mention :-) I have read your source code, and I found it's similar to the source of the email client embedded in the Android source code now. My one question is, the cause that 3rd-party applications could not create a SSL socket, is because of 3rd-party applications can not create / access the already existed KeyStore file in the system?
If my observation is right, do we just only need to create a local KeyStore file and assign this file to the original TrustManagerFactory for access it? The reason why I ask this is I followed the architecture in the AndroidHttpClient, and found that in the Apache SSLSocketFactory there already has 2 managers: keymanagers and trustmanagers. It seems we need to assign 2 store files at the construction stage of SSLSocketFactory. Another question is, where (or when) should I know there is a new SSL certification needs to be notified, and accepted (or not) by the user? I saw the "acceptKeyDialog" in your AccountSetupCheckSettings.java, however I have no idea about when this dialog will be triggered. and appreciates for you and your project again, that really helps a lot! ;-) Best regards, Nicholas On 12月21日, 下午1時07分, "Bradley Young" <young.brad...@gmail.com> wrote: > Al and Michael, > > Thanks for the ego boost. I certainly would appreciate eyes on my code. > The one thing that I will add: while there are standard libraries for > crypto, they are also some of the worst documented (my opinion) in the > entire java suite. > > Nicholas, > > Feel free to contact me if you have questions about the implementation. > Michael is correct; the implementation exists almost solely in the > TrustManagerFactory.java, but there are some UI bits in the > activity/setup/AccountSetupCheckSettings.java (specifically, there's some > insight into how to present the certificate chain to the user). > > Also, just for reference, we recently completed the grand re-renaming > (moving most everything back into the com.android.email namespace, to > facilitate merging with the mainline), so don't go looking in com.fsck.k9. > > Bradley > > On Fri, Dec 19, 2008 at 7:23 AM, Michael <michael573...@gmail.com> wrote: > > > I second the mention of using K9 as reference. Check in the src/com/ > > fsck/k9/mail/store/ directory, specifically the ImapStore.java and > > TrustManagerFactory.java files, among others. > > > Also note that this stuff isn't Android-specific, these are standard > > java.* and javax.* libraries, and there's lots of examples on the 'net > > about using them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
