3 ms·
Isn't that what Let's Encrypt is aiming for? Install a package, which configures a cronjob for you? https://letsencrypt.org/howitworks/ https://letsencrypt.org
by geofft 11y ago
Isn't that what Let's Encrypt is aiming for? Install a package, which configures a cronjob for you?
https://letsencrypt.org/howitworks/ https://letsencrypt.org/howitworks/
Which could just even become a default but optional dependency of your distro's web server package, or part of your Docker container, or whatever.
- Nullabillity 11y agoI tried to set up LE for my personal bunch of websites, but sadly the rate-limiting is still too strict for automation to be a viable option.
- geofft 11y agoHuh, the rate limits look pretty generous (500 certs every 3 hours): https://community.letsencrypt.org/t/rate-limits-for-lets-encrypt/6769 https://community.letsencrypt.org/t/rate-limits-for-lets-enc... Do you actually own hundreds of personal websites? (And you could still desync them, anyway.) Or is this a use case where wildcards would be useful. I sort of disagree with LE's decision to not care about wildcards for now, though I understand that it's simpler, at least while it's in beta.
- Nullabillity 11y agoThat's per IP, you're also limited to 5 requests per domain name per week. In my case, I have a bunch of subdomains for various stuff that all counts against the limit for the main website. I suppose I ought to combine the CSRs, but implementing that makes it a bit more complex than just automatically requesting a certificate per nginx vhost.
- geofft 11y agoOh, that's pretty rough. Still, with enough automation, you can request 5 per week in a cronjob, which will let you get at least 40-something websites, even with the recommended 60-day renewal cycle. :-P
- Dylan16807 11y ago>you're also limited to 5 requests per domain name per week Huh, I'm pretty sure I used more than that when I was first setting it up with no problems.
- Nullabillity 11y agoTo quote the website: > Certificates/Domain you could run into through repeated re-issuance. This limit measures certificates issued for a given combination of Public Suffix + Domain (a "registered domain"). This is limited to 5 certificates per domain per week.
- pfg 11y agoIf SAN certificates make sense for your setup (i.e. all used on the same server or for the same service), you can have up to 100 (sub)domains on one certificate, or basically 500 per week. Maybe that's how you managed to get more than 5.
- Dylan16807 11y agoI did a bunch of requests starting with one subdomain, then a second, adding SANs multiple times, setting a cron to do one request a month and testing it, then adding yet one more SAN to the list.
- blakeyrat 11y agoOk I'm new to this and I know it's still beta, but it seems: 1. Still WAY too complicated (look at all the stuff you have to know and type) 2. Doesn't seem to support my preferred OS (Windows) or web server (IIS) what-so-ever. Which is strange since, from my experience, installing certs in IIS is already far easier than in Apache and Nginx. (Although maybe that's why they perceive it as less of a priority?)
- schoen 11y agoHi, I think the IIS support effort that's furthest along is described at https://community.letsencrypt.org/t/how-letsencrypt-work-for-windows-iis/2106 https://community.letsencrypt.org/t/how-letsencrypt-work-for... ; maybe that will be useful for you if you want to try Let's Encrypt on your IIS system. We've had hundreds of people remark that they found Let's Encrypt faster and easier to use than other CA offerings (though most of those people were using Apache on Debian-based systems), so I think we are getting somewhere. But we definitely hope that upstream web server projects and hosting environments will integrate ACME clients of their own, like Caddy has done, so that eventually most people won't need to run an external client at all and won't have to worry about compatibility or integration problems.
- cyphar 11y ago> 1. Still WAY too complicated (look at all the stuff you have to know and type) I didn't realise that people getting SSL certs and administrating servers don't know how to read a literally one-page rundown of what to run. They also have helper scripts to make it much simpler. > Which is strange since, from my experience, installing certs in IIS is already far easier than in Apache and Nginx. (Although maybe that's why they perceive it as less of a priority?) nginx literally takes less than 10 minutes to set up not only SSL, but also CSP and several other very important security features.
- yoz-y 11y agoLet's Encrypt is awesome but you still need to have root access to the machine. I host my stuff on a shared 1&1 node and I can't seem to find any way to add SSL to my websites without having to pay them. (Yes I should move to another host but that is too much hassle for me right now.)
- clinta 11y agoThe ACME protocol is open and as a result there are several alternative clients which do not require root. Here's a few: https://github.com/diafygi/letsencrypt-nosudo https://github.com/diafygi/letsencrypt-nosudo https://github.com/kuba/simp_le https://github.com/kuba/simp_le https://github.com/lukas2511/letsencrypt.sh https://github.com/lukas2511/letsencrypt.sh Or you can go a more manual approach via https://gethttpsforfree.com/ https://gethttpsforfree.com/ but you will need to manually renew your certificate every 90 days.