7 ms·
I second this experience, and "Lovecraftian" is indeed an excellent way to describe it. It's not just that the process was difficult, it's that my confidence dw
by aiurtourist 15y ago
I second this experience, and "Lovecraftian" is indeed an excellent way to describe it. It's not just that the process was difficult, it's that my confidence dwindled through every strange and baffling step.
Since you mentioned paying "a few dollars" to Namecheap, can you comment on the feasibility of their $8.95 "PositiveSSL" certificate? ( http://www.namecheap.com/ssl-certificates/comodo.aspx http://www.namecheap.com/ssl-certificates/comodo.aspx )
- ohgodthecat 15y agoCan you extrapolate on what you mean by feasibility, I use positive SSL on a few domains it works fine with no issues and isn't that hard to setup (basically you just need to be able to receive email on your domain).
- foobarbazetc 15y agoThe best (in terms of browser compatibility) cheap cert that Namecheap sell is the RapidSSL cert at http://www.namecheap.com/ssl-certificates/geotrust-ssl-certificates.aspx http://www.namecheap.com/ssl-certificates/geotrust-ssl-certi...
- moe 15y agoBe aware though that GeoTrust and Thawte certs don't work[1] on android devices. There are claims that it can be fixed by adding a cross-root cert[2] but for me that didn't work out. More generally: If you need to support mobile devices then read your CA's compatibility list closely (if you can find it...) and test, test, test. You'd think this shouldn't be an issue anymore in 2012, but it sadly still is. [1] http://www.zimbra.com/forums/administrators/44675-new-geotrust-ssl-certificates-android-users.html http://www.zimbra.com/forums/administrators/44675-new-geotru... [2] https://support.servertastic.com/entries/426677-rapidssl-and-geotrust-certificate-not-trusted-on-mobile-device https://support.servertastic.com/entries/426677-rapidssl-and...
- yuhong 15y agoMore precisely, older Android devices.
- foobarbazetc 15y agoSigh. I spent way too much time picking these particular certs and they've gone and messed it up. :) The cross-root cert should work, but you need to make sure it's presented in the right order, I think. FWIW, my latest RapidSSL-through-Namecheap certs were issued by: issuer=/C=US/O=Equifax/OU=Equifax Secure Certificate Authority And that's the "good"/trusted CA. I'm not sure when they made the switch, but I only got this cert issued a couple of months ago. FWIW, we also support Docomo phones, and that is a huge pain in the ass. The only CA that works there is: i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority If you don't need to support really old mobile devices, the best certs going are, IMHO, Digicert. They get chained all the way back to Entrust: 1 s:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV CA-1 i:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV Root CA 2 s:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV Root CA i:/C=US/O=Entrust.net/OU=www.entrust.net/CPS incorp. by ref. (limits liab.)/OU=(c) 1999 Entrust.net Limited/CN=Entrust.net Secure Server Certification Authority And the company has some of the best customer service going anywhere.
- xxqs 15y agoI have a Comodo certificate purchased through cheapssl.com. There is one problem: some older android 2.3 phones don't recognize it as valid and refuse to download any non-html data files.
- xxqs 15y agofixed it by installing the intermediate chain on my server