Their goal may be to have their CA included in major browsers, but I don't think they are there yet. When I went to their sign-up page, which goes to their secure domain, neither Mozilla nor FireFox recognized their CA so both gave me a certificate warning. So it just depends on how seamless you want the SSL on your site to be for the people who browse it. If you get a cert from this CA, or self-sign one, then people will most likely see the browser warning when they first encounter it, and will have to accept it before they can see your SSL-protected content. If you pay for a cert, you will not be as likely to have this problem because more browsers will already have the CA in them by default. And generally the more you pay for the cert, the more browsers will support your CA/cert already.
-Loren -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott Jackman Sent: Wednesday, March 02, 2005 11:40 AM To: Provo Linux Users Group Mailing List Subject: Certificate Authority There was a discussion a couple of months ago about cheap certificate authorities, and it was mentioned that GoDaddy had a $29 product. I have a small non-commercial web-site that I want to enable SSL on. In my research I found www.cacert.org which does free SSL certificate signing. Has anyone used or heard of CAcert and can tell me why I should or shouldn't use this service over GoDaddy or a larger entity such as Veri$ign? .===================================. | This has been a P.L.U.G. mailing. | | Don't Fear the Penguin. | | IRC: #utah at irc.freenode.net | `===================================' .===================================. | This has been a P.L.U.G. mailing. | | Don't Fear the Penguin. | | IRC: #utah at irc.freenode.net | `==================================='
