Installing new certificates on Android

May 12, 2012

Recently I’ve encountered a website that is using the certificate “Verisign Class 3 Secure Server CA – G3”. Unfortunately, my Android device (Samsung Infuse running Froyo 2.2.1) doesn’t know about that certificate, so I get a warning.

Installing a certificate on this device is not hard, but there are one or two tricks.

First, download the certificate. For me it was a Verisign certificate. I did a search on the certificate title and determined it corresponded to the Verisign cert SVRSecureG3.cer, so I went to crl.verisign.com and grabbed it. (Note that .cer is the certificate and .crl is the certificate revocation list.)

Once you have the .cer, it’s unfortunately in binary mode. Use openssl (which is included as part of Cygwin for Windows users) to convert it to a .crt:

$ openssl x509 -in SVRSecureG3.cer -inform DER -out SVRSecureG3.crt -outform PEM

Install that .crt on the root of the removable SD card. For Samsung devices, this means it will have to be in /mnt/sdcard/external_sd/.

Go to the Settings app, and select “Location and security”, then “Install encrypted certificates”. You will be prompted with a dialog for the Certificate name; I just took the default. Click “OK”.

You’ll be prompted to enter a password for credential storage. Do not forget this password.

At this point, the credential has been imported. Next time you visit the website, you should not get a bad certificate.


Rooting the Samsung Infuse with SuperOneClick

May 6, 2012

After spending ages trying to root my Samsung Infuse (i997) running Android 2.2 with SuperOneClick on my Windows XP box, I finally did the right thing: blew it away and installed Windows 7. With that, I was able to root the Infuse this afternoon.

I used:

After rooting, I rebooted the device. It worked with no problems. I shot the developer of SuperOneClick a donation ’cause why not.

Later I installed TitaniumBackup, which gave me a warning message about the access rights to su and offered to correct it. I said to go ahead and it did:

Access rights on the “su” binary were successfully correced from “0:2000 [6755]” to “0:0 [6755]”. Please reboot your device for the changes to apply.

I think that changed it from root.shell to root.root.

At any rate, now I know I can root the Infuse.

I wasn’t able to root an Infuse running 2.3.5 Gingerbread. Instead I had to use this XDA post, Odin, and reflash a new ROM.