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
There is a very good reason why applications shouldn't be able to add
certificates to the system keystore, and that's security.
If an application wants a user to trust a certificate for the actions
the application it's performing then that is decision made by the user
in the context of that
I see :-)
It sounds good for this security mechanism. However, I still don't
know how to make an application-specific keystore for certain
application only...
And it sounds that Android has already provided a way for applications
to safely create their own certification rather than system
I'm sure the K9 guys wouldn't mind you looking over their code;
http://code.google.com/p/k9mail/source/browse/k9mail/trunk/src/com/android/email/mail/store/TrustManagerFactory.java
Al.
http://andappstore.com/
yukinoba wrote:
I see :-)
It sounds good for this security mechanism. However, I
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
hi,
I have surveyed lots of solutions to this problem. However, most
solutions break (or say, cheat) the SSL verification for development
usage, and surely I don't want to make this kind of solutions in my
own application. Could you help to provide a guideline how to create
application-specific
Yep, join the club. Lots of us are complaining about the inability to
add certificates to the system keystore.
One way that people have been working around this (in apps like
k9mail, for example), is to use an application-specific keystore.
--~--~-~--~~~---~--~~
7 matches
Mail list logo
