{"id":831,"date":"2007-07-06T20:54:31","date_gmt":"2007-07-06T19:54:31","guid":{"rendered":"http:\/\/www.markwilson.co.uk\/blog\/2007\/07\/low-cost-ssl-certficates-from-go-daddy.htm"},"modified":"2008-12-31T20:08:43","modified_gmt":"2008-12-31T20:08:43","slug":"low-cost-ssl-certificates-from-go-daddy","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2007\/07\/low-cost-ssl-certificates-from-go-daddy.htm","title":{"rendered":"Low cost SSL certificates from Go Daddy"},"content":{"rendered":"

I have a number of web services running at home, some of which are SSL secured; however, they are only used by me (and a few select friends and colleagues) so, in theory, I could generate certificates by creating my own public key infrastructure<\/a> (PKI) and add my certificate authority (CA) to the Trusted Root Certificate Authorities store. The trouble is that I’m lazy, and a CA is just another infrastructure service to run (it really is a bit geeky to have as many computers as I do), so I use a public certificate instead.<\/p>\n

Because I don’t require the highest levels of validation, I don’t need an expensive certificate from a class 1 CA like Verisign so last year I used a free certificate from Ascertia<\/a>. No matter how hard I tried, I couldn’t complete the certification path or get clients to trust the Ascertia root certificate, but last night, Scotty McLeod<\/a> mentioned low-cost certificates from