3 ms·
I'm also not a fan of LE, for some (but not all) of the reasons stated here. I particularly hate the short cert lifetimes (that they intend to make even shorter
by JohnFen 3y ago
I'm also not a fan of LE, for some (but not all) of the reasons stated here. I particularly hate the short cert lifetimes (that they intend to make even shorter).
- brohee 3y agoCRL are a failure, OCSP can't scale, so to get some assurance that if the private key was compromised somewhat recently, it's either mandating OCSP stapling or shorter lived certs... Why do you hate the short lifetimes?
- dale_glass 3y agoWhy can't OCSP scale? Doesn't stapling help a lot with that?
- brohee 3y agoStapling works, but is a lot more useful if it is mandatory (which it is not). OCSP as intended in the early 2000s where the client query the CA is a non starter, the hosting cost would be such that not only free certificates would end but the paying one would be much more expensive. I think most people will find short lived certificates more convenient than mandatory OCSP stapling.
- JohnFen 3y ago> Why do you hate the short lifetimes? Because they require more frequent maintenance. That has to happen either manually or through automation. LE seems to think that automation means that short lifetimes aren't painful, but I disagree -- if for no other reason than that there are plenty of places where automation is not feasible.
- brohee 3y agoLet's Encrypt isn't exactly hiding that it's only practical in the context of automation From their FAQ (https://letsencrypt.org/docs/faq/ https://letsencrypt.org/docs/faq/): What is the lifetime for Let’s Encrypt certificates? For how long are they valid? Our certificates are valid for 90 days. You can read about why here. There is no way to adjust this, there are no exceptions. We recommend automatically renewing your certificates every 60 days.
- JohnFen 3y agoRight. I never claimed that LE was hiding this fact. I'm just saying that requirement is very problematic for me and makes LE a suboptimal solution for my purposes.
- ryandrake 3y agoI agree with this. I use L.E. for a handful of hobby domains, and it seems every 3 months, something fails, and I have to ssh in and diagnose and re-run something and restart some processes. Yuck. I’d rather just get/configure certificates once, and not have to worry about them anymore. This feels like software that deletes its own config file every three months, just to make you write a script that regenerates the config. Make-work. It would be great to have a button “I understand the risks, give me a 5 year certificate.”
- remram 3y agoWhat's your issue with short lifetimes?
- JohnFen 3y agoI answered this in a different comment. TL;DR is that short lifetimes bring greater maintenance requirements, and automation is not always helpful.
- remram 3y agoYou're rephrasing your claim, not providing any argument. If renewal is automated correctly, why would it bring more maintenance? When is automation not helpful? If my automation is broken, I would rather find out sooner than later... or having to find out the previous guy set it up wrong. Wouldn't you?
- JohnFen 3y agoMy claim is that I have situations where automation is not feasible to implement, not that I have trouble correctly setting it up. People are downvoting my comments here, no surprise, so I feel compelled to clarify: I am not saying that others shouldn't use LE, nor am I saying that LE is without value. I am acknowledging that LE is not a panacea and brings its own complications that have to be considered. In my case, LE is not a solution that works for me. Instead, I buy the certs for my websites that are used by the general public, and run my own private CA with my own root cert that is used to mint certs for everything else.
- remram 3y agoI would love to hear more about your issue though. I have deployed LE in situations where I needed wildcard certs and didn't have access to the DNS server to set the challenge (literally a separate network) successfully. I have deployed it in situations where the DNS server doesn't even have an API at all. I won't claim that it is always easy, but I really can't object to the short lifetime. I agree that the goal should be to automate this. After all, domain registrations aren't forever, you shouldn't be able to hold on to certificates to someone else's domain.