How is this reasonable? What is their threat model? Did they even consider that this directly threatens availability to those that don't automate everything? Soon certs become a blocker for backups. The 63-day old snapshot of infra is on the edge of useless in an emergency.
I don't mind 64-day certificates. However they recommended renew at 2/3 validity remaining means that I can no longer take a month off without needing to be prepared to debug a certificate re-issuance problem. Not a problem for companies with 24/7 oncall or even at most a week of the whole company off at a time. But for individuals this is pretty annoying.
Sure, re-issuance usually works. But when you only do it every 42 days it does break from time-to-time without you noticing.
I would love if we still renew with 30d remaining. I really don't care if they reduce certificate lifetime to 31 days as long as I am allowed to renew daily. But lowering the gap between expiry and when you are allowed to renew is very annoying.
Be ready because their plan is to reduce the lifetime to 7d as soon as possible for their evil masterplan to strip us off reasonable control about our websites.
Now that they have a dominant position they do Google style and Google influenced move.
You are at their will fit whatever retarded dictatorial decision they want.
Given this is a free service, what's the endgame of this "evil plan"? I don't know much about SSL and such so I assumed lowering this lifetime has some safety benefit
What about the things ACME can't automate? Word around the shop is that this is basically Apple making this change and forcing everyone else in the group to follow along
Thank you for sharing this because I utilize LetsEncrypt for my services. I especially liked the guidance on automated renewals as the expiry period is now short enough to justify automating it. I'm currently doing it manually but a cron that runs a bash script for this is plenty.
How is this reasonable? What is their threat model? Did they even consider that this directly threatens availability to those that don't automate everything? Soon certs become a blocker for backups. The 63-day old snapshot of infra is on the edge of useless in an emergency.
I don't mind 64-day certificates. However they recommended renew at 2/3 validity remaining means that I can no longer take a month off without needing to be prepared to debug a certificate re-issuance problem. Not a problem for companies with 24/7 oncall or even at most a week of the whole company off at a time. But for individuals this is pretty annoying.
Sure, re-issuance usually works. But when you only do it every 42 days it does break from time-to-time without you noticing.
I would love if we still renew with 30d remaining. I really don't care if they reduce certificate lifetime to 31 days as long as I am allowed to renew daily. But lowering the gap between expiry and when you are allowed to renew is very annoying.
Be ready because their plan is to reduce the lifetime to 7d as soon as possible for their evil masterplan to strip us off reasonable control about our websites.
Now that they have a dominant position they do Google style and Google influenced move.
You are at their will fit whatever retarded dictatorial decision they want.
Given this is a free service, what's the endgame of this "evil plan"? I don't know much about SSL and such so I assumed lowering this lifetime has some safety benefit
What about the things ACME can't automate? Word around the shop is that this is basically Apple making this change and forcing everyone else in the group to follow along
How long until 1 hour certificate lifetimes?
Thank you for sharing this because I utilize LetsEncrypt for my services. I especially liked the guidance on automated renewals as the expiry period is now short enough to justify automating it. I'm currently doing it manually but a cron that runs a bash script for this is plenty.