I am struggling with Android 4.0, trying to connect with websites over an TLS connection. With the pre-installed root certificates everything works as expected, but with certificates that depend on a user-installed CA certificate there seems to be some fundamental problem. I tried it with the default Browser, Chrome and Firefox on a Motorola xoom (Android 4.0.4):
- with "Browser", I can install the CA certificates (they show up in settings/... afterwards), but every attempt to connect with a server that uses a certificate that is signed by the installed RootCA causes a crash
- Firefox crashes when downloading/installing the root certificate; connecting to a web server works, but of course without the root certificate the authenticity can't be verified
- Google Chrome produces a mixture of both - it will download & install the root certificate, but when connecting to the server it considers the server certificate as untrusted. When requesting detailled information about the certificate, it will show just the heading (something like "certificate viewer"), but no certificate
There seems to be a general problem with android 4.0 - I tried the same thing with AndroidX86 in a VM (only with the pre-installed Brwoser because the App store won't allow the device) with pretty much the same results.
Does anybody have any idea, what's going on? Searching google I couldn't find anything about this issue. I see the problem with 2 different root certificates, that are both issued with openssl, but otherwise have little in common. Fascinatingly, accessing WLANs using similar certificates works as expected ...
- with "Browser", I can install the CA certificates (they show up in settings/... afterwards), but every attempt to connect with a server that uses a certificate that is signed by the installed RootCA causes a crash
- Firefox crashes when downloading/installing the root certificate; connecting to a web server works, but of course without the root certificate the authenticity can't be verified
- Google Chrome produces a mixture of both - it will download & install the root certificate, but when connecting to the server it considers the server certificate as untrusted. When requesting detailled information about the certificate, it will show just the heading (something like "certificate viewer"), but no certificate
There seems to be a general problem with android 4.0 - I tried the same thing with AndroidX86 in a VM (only with the pre-installed Brwoser because the App store won't allow the device) with pretty much the same results.
Does anybody have any idea, what's going on? Searching google I couldn't find anything about this issue. I see the problem with 2 different root certificates, that are both issued with openssl, but otherwise have little in common. Fascinatingly, accessing WLANs using similar certificates works as expected ...