5 ms·
I strongly dislike wildcard certificates. I worked in a few places that had a *.company.com which covered, obviously, everything under that domain. That meant
by dijit 9y ago
I strongly dislike wildcard certificates.
I worked in a few places that had a *.company.com which covered, obviously, everything under that domain.
That meant if that wildcard cert leaked then our EV cert for, say, checkout.company.com would be essentially compromised too.
Not to mention. If you have a wildcard cert it's rather likely you're passing those certs around servers, lots of scope for leakage.
I really think that if you feel the need to do wildcard certificates, then you should at least try to figure out another way around it. I'm not saying you absolutely must never use them, but be incredibly mindful of what is at stake and limit the scope and availability of such certs as much as possible.
For instance. Don't put the same wildcard on mail servers and IM servers and git servers and etc; a compromise of one will compromise them all and the revokation system is not good enough.
https://blog.dijit.sh/please-stop-advocating-wildcard-certificates https://blog.dijit.sh/please-stop-advocating-wildcard-certif...
- Shorel 9y agoA big part of that was cost. A wildcard certificate can be used to lower costs if a company has hundreds of sub-domains. But now, with the full LE offer of services, cost is no longer an issue, and all you mention should be easily automated via scripts.
- mnutt 9y agoI agree that wildcards aren't great if they're being passed around an organization to avoid registering a few extra certs, but they are very useful in a few circumstances such as sandstorm.io: every app session uses a different subdomain to prevent cookie leakage, and registering that many certs would overwhelm LE. I'd imagine there are other cases out there involving automatically created subdomains that will benefit.
- dijit 9y agoLike I said. There are uses for wildcard certs I'm just arguing against the fact they're used en masse. People should be perfectly aware of the ramifications and sandbox appropriately. (*.tennant.sandstorm.io or whatever.) Everyone keeps saying SaaS is the reason for the use of wildcard certs and I would absolutely argue the point that multi-tennancies weakest tenet is the fact that if you get compromised the scale can be broad. Why intentionally weaken that system? LE can handle thousands of domain creations a minute, they've been very forthcoming with lifting limits for people on domain creation. The downside is your server sites which need a little overhead for vhost creation but that could be automated with less than a day of ops work.
- pas 9y agoStoring that many certificates is a total waste of engineering. (On both LE's and the SaaS's side.)
- mnutt 9y agoI believe a while ago the sandstorm people spoke to LE who advised that it wasn't a good idea. I'll stand by the assertion that vhosts are probably still better off with a wildcard cert if it's the difference between a single server using a single cert vs a single server holding thousands of certs. In a node compromise it's the same either way. If different servers are serving different subdomains then sure, subdomain certs are the better way to go.
- ocdtrekkie 9y agoI'll probably finally self-host Sandstorm once I can get a wildcart cert from Let's Encrypt.
- the_common_man 9y agoWas this the main issue stopping you? Wildcard certs are only 45 USD per year.
- ocdtrekkie 9y ago$45 a year from who? I didn't see anything that cheap from anywhere mildly reputable. And yeah, main reason.
- edgan 9y agoAlphaSSL, Google $42 wildcard
- the_common_man 9y agoGarrison host, ssl2buy
- hakanensari 9y agoThere are legitimate use cases: for instance, a multi-tenant app that designates tenant by subdomain.
- dijit 9y agoI would argue that they're useful but not mandatory. Is having separate certs really that big of a deal? Operational overhead with LE is next to none and if you're scared of hitting limits you can contact LE to have the limits increased.
- minitech 9y agoRequesting a new certificate per user is another step that can go wrong, and contacting LE for limit increases is a barrier.
- maccard 9y agoCouldn't you have a cert per sub domain? If you're using Let's encrypt, you almost certainly have automated renewal in place, so you could allocate a cert when you give them a subdomain
- ceejayoz 9y agoYou can only put 100 domains on a Let's Encrypt cert, so if you're a site like Tumblr that's going to be a whole bunch (hundreds of thousands or millions of certs) of mayhem.
- tapvt 9y agoThis is great advice, and, honestly, an issue I had not given enough thought. So, thanks. I've often (always?) fallen into the trap of "Let's just use a wildcard. Setting these things up is a pain in the ass!"
- Faaak 9y agoBut wildcards are useful when you have 2 or three front-end load balancers. They are only replicated twice, which is reasonable IMHO.
- binarymax 9y agoFor the cases you mention, I mostly agree. Wildcard certs are critical for many SaaS use cases though, where you need a cert for each customer on a product domain: company1.example.com, company2.example.com, etc.
- dijit 9y agoI would argue that they're useful but not mandatory. Is having separate certs really that big of a deal? Operational overhead with LE is next to none and if you're scared of hitting limits you can contact LE to have the limits increased.
- pfg 9y agoI don't think it's fair to say the operational overhead would be next to none. As it stands right now, most services that use per-user subdomains get wildcard certificates. Let's assume that wouldn't be an option for a service like tumblr, which has per-user subdomains. They have ~350 million users, that's not really practical to maintain. And that's just one big site, there are plenty of others. This would not just overwhelm the issuance capacity of most CAs, but it would also be a problem for many other components of the Web PKI, like Certificate Transparency log servers, which have so far only needed to handle a total of ~450 million certificates (many of which are duplicates that have been logged to multiple servers). There's certainly a place for wildcard certificates, but I definitely agree that they should be used sparingly.
- pfg 9y agoThis is definitely true, and single-domain or SAN certificates should continue to be the first option administrators consider when deploying TLS. Wildcards make sense for things where the number of subdomains is unmanageable and where each of those subdomains share the same attack vector (i.e. are handled by the same load balancer, etc.) The fact that validation for wildcard certificates is limited to the DNS challenge will hopefully ensure that most users will continue to use non-wildcards, as the other challenges are significantly easier to automate.
- prdonahue 9y agoFor those concerned with others in their organization obtaining/using wildcards unsafely: set a CAA record prohibiting wildcard issuance from any CA and be done with it.