Re:Ask HN: For a startup which SSL certificate authority wou...
by skrish on Monday January 02, 2012 @02:54AM
(#3415192)
Thanks. For my SAAS app where I need to issue <<customername>>.<<mydomain>>.com it will be very expensive to start with if I do not go for wildcard.
I understand the risk & re-certification issue and will look into this further.
Re:Ask HN: For a startup which SSL certificate authority wou...
by marshray on Monday January 02, 2012 @03:07AM
(#3415217)
You should fully understand the same-origin implications of such a design before deploying it.
For example, if <<customername>> is able to set cookies or run script (e.g., via XSS), they will be able to set cookies that affect everything under <<mydomain>>.com. Under some circumstances they will even be able to read back the values.
Here's a good site to keep you awake at night: http://lcamtuf.blogspot.com/2010/10/http-cookies-or-how-not-...
Once you have a wildcard cert, you'll find all kinds of places you want to start using it...the web site, the production system, the blog, the mail server, the remote access server, and so on. But effectively they mean that if, say, your blog gets pwned, then everything in your production is pwned and has to be revoked and re-certificated (and the security advisory is much uglier).
Find an inexpensive one of the top 10 CAs (other than GoDaddy of course) - it hardly matters which. IMHO there's no reason you should have to pay per-server for a cert. It makes disappointingly little difference who you go with on the server side, especially if you generate your own keys and CSR, then the CA never even sees your private key.
Comodo's private key was not hacked. They did issue some fraudulent certs through hacked resellers, but that compromised the security of all users equally.