“if you have to replace the certificate every 64 days or something, you're definitely going to want to automate that. You're not doing that by hand every 60 days or you're going to screw up frequently.”

…if you have to go and change because you lost your Acme account or whatever, then your site's going to be going through an outage until the DNS change propagates. So definitely don't jack it up too long, but there may be value in that actually being a day or two instead of only minutes or hours.

Well, something related that I saw was 64-day certificate lifetimes coming in February 2027 for Let's Encrypt.

For most people using Let's Encrypt, this change isn't something that you're really going to need to do anything to accommodate. If you're using CertBot with its standard installation and it's automatically installed cron jobs or systemd timers, you're all set. It's checking to see if there's a new…

They also mentioned they are reducing the authorization reuse period from 30 days down to 10. And in 2028, it will shrink to just seven hours to comply with the new 2029 rules, reducing the maximum validation reuse period and to remove the need for CAA rechecking, where we have to repeat part of…

Ubuntu 2610 is dropping support for a bunch of file systems, including ZFS, for the boot partition if you're using secure boot.