3 ms·
Not always possible in all scenarios. For a setup like github.io and github pages it'd be difficult for LE to handle so many domains. Or any scenario where yo
by simcop2387 10y ago
Not always possible in all scenarios. For a setup like github.io and github pages it'd be difficult for LE to handle so many domains. Or any scenario where you serve a subdomain up without knowing ahead of time what it'll be (say a tor relay service) it's just not feasible.
- kbenson 10y agoWhat's the turnaround time for LE? Could you possibly deneract an LE certificate on the fly as needed when the request is sent (just block until it's present to be served)? Not that I would really suggest this, it's a DOS waiting to happen.
- josegonzalez 10y agoDokku can do it in [two commands](https://github.com/dokku/dokku-letsencrypt#usage https://github.com/dokku/dokku-letsencrypt#usage): dokku config:set --no-restart myapp DOKKU_LETSENCRYPT_EMAIL=mail@example.com dokku letsencrypt app
- Xorlev 10y agoThe problem is the volume of certs needed, not the simplicity of LE for the smaller usecase.
- Lxr 10y agoThere're limits to the amount of subdomain certs you can request, so I imagine this wouldn't work. https://letsencrypt.org/docs/rate-limits/ https://letsencrypt.org/docs/rate-limits/ > Combined with the above limit, that means you can issue certificates containing up to 2,000 unique subdomains per week.
- tajen 10y agoLetsEncrypt's software is open-source. A commercial CA could use it, remove the limits and add EV if they wanted, then lower their costs to $50 per domain: much lower and much more trustworthy than Symantec...