there is no great way to support self-signed certs in collect.
it's a long standing bug
(http://code.google.com/p/android/issues/detail?id=11231) and there aren't a
lot of good solutions.
http://stackoverflow.com/questions/2642777/trusting-all-certificates-using-httpc
lient-over-https/6378872#6378872 has a good discussion.
what we could do is create a custom socket factory that uses the default
android cert keystore, but falls back on a compiled into collect store if the
server fails to verify with the default. then in that alternate keystore, we'll
maintain a list of some of the popular root cas (and people could compile in
their self-signed certs).
this seems like a lot of work for very little benefit. using certs from most of
the popular places seems easy enough. just want to document this and make it an
explicit wont fix.
Original issue reported on code.google.com by yanokwa on 27 Jul 2011 at 9:10
Original issue reported on code.google.com by
yanokwaon 27 Jul 2011 at 9:10