Generic instructions on how to make them can be found on the Windows Mobile blog.
A premade CAB file with both the Class 1 and Class 3 certificates can be found at
This doesn't happen very often but it is becoming a bit of a pain when it does happen.Some phones' Android systems do not include this program.In such a case, you have to store all certificates added as the user ones. It should list both "CAcert Inc." and "Root CA" among the other certificates in the 'System' section.* On Windows Mobile2005 you need to download the DER-Encoded certificate (pocket IE cannot save it, so you need to store it in a zip-file for download.) * Then you need to rename it to .Only then will you be able to install it with a double-click.However, there are some distributions about which we know some information, listed below.Before Android version 4.0, with Android version Gingerbread & Froyo, there was a single read-only file ( /system/etc/security/) containing the trust store with all the CA ('system') certificates trusted by default on Android.There are many ways to ensure that you have an authentic, non-tampered copy of the root certificates, all of which boil down to having a trusted party verify the certificate fingerprints.In some cases, your system distribution is the trusted party, but you can also verify it for yourself.Installing CAcert certificates as 'user trusted'-certificates is very easy.Installing new certificates as 'system trusted'-certificates requires more work (and requires root access), but it has the advantage of avoiding the Android lockscreen requirement.