Ehhhh, so I get why you made this, but at the same time, LetsEncrypt intentionally chose 90 days for the duration of the certs. Presumably because renewing a cert is a positive confirmation that you still retain ownership. You <i>actively</i> performed an action that declared: hey I still retain control of this and it hasn&#x27;t been compromised. (as opposed to other states your cert could be in -- abandoned, compromised, password forgotten and you were too lazy to get the cert revoked-- trust me, engineers made cron because we were lazy especially when it comes to mundane things).<p>This is around-about way of saying that 90 days was a well-thought out duration to issue a cert and the process of renewing it <i>manually</i> is there as a positive (rather than passive) confirmation you retain control. These guys are doing a public service, on par with archive.org and the EFF. I&#x27;m not sure, but even though I&#x27;ve been using cron since before I was a teenager, I&#x27;m not throwing that entry in.<p>Edit: Whoops, so I was half-wrong, mea culpa.
<a href="https:&#x2F;&#x2F;letsencrypt.org&#x2F;2015&#x2F;11&#x2F;09&#x2F;why-90-days.html" rel="nofollow">https:&#x2F;&#x2F;letsencrypt.org&#x2F;2015&#x2F;11&#x2F;09&#x2F;why-90-days.html</a> Part 1 addresses the security issue I brought up, and part 2 endorses automation. My mistake.