3 ms·
Couldn'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
by maccard 9y ago
Couldn'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.
- maccard 9y agoYou can contact Let's Encrypt to get those limits lifted I believe?
- ceejayoz 9y agoThat's not going to help. Every time someone adds a domain to Tumblr, they'd have to re-do the certbot challenges for all 50 MILLION domains. Plus, all 50 million domains are listed IN the certificate. It'd be megabytes worth of additional data for every visitor to Tumblr. *.tumblr.com makes a lot more sense.
- Whitestrake 9y agoI agree with the case for using a wildcard, but just to play devil's advocate - why can't they take the CloudFlare approach? Generate a cert for 100 of your client's domains, use that cert across those domains. Cut your 50m domains down to 500,000 certificates. Serving the right certificate for the right domain is a simple enough task. As new tumblr domains are registered, generate more certs in batches of 100 domains. I doubt anyone would ever seriously suggest putting millions of SANs on a single certificate, but 100 isn't too farfetched.