Let’s Encrypt will be reducing the validity period of the certificates we issue. We currently issue certificates valid for 90 days, which will be cut in half to 45 days by 2028.
This change is being made along with the rest of the industry, as required by the CA/Browser Forum Baseline Requirements, which set the technical requirements that we must follow. All publicly-trusted Certificate Authorities like Let’s Encrypt will be making similar changes. Reducing how long certificates are valid for helps improve the security of the internet, by limiting the scope of compromise, and making certificate revocation technologies more efficient.

  • Passerby6497@lemmy.world
    link
    fedilink
    English
    arrow-up
    27
    ·
    10 hours ago

    I’ve been dreading this switch for months (I still am, but I have been, too!) considering this year and next year will each double the amount of cert work my team has to do. But, I’m hopeful that the automation work I’m doing will pay off in the long run.

      • Passerby6497@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        ·
        10 hours ago

        Personally, yes. Everything is behind NPM and SSL cert management is handled by certbot.

        Professionally? LOL NO. Shit is manual and usually regulated to overnight staff. Been working on getting to the point it is automated though, but too many bespoke apps for anyone to have cared enough to automate the process before me.

        • groet@feddit.org
          link
          fedilink
          English
          arrow-up
          3
          ·
          3 hours ago

          One reason for the short certs is to push faster adoption of new technology. Yes that’s about new cryptography in the certs but if you still change all your certs by hand maybe you need to be forced …

    • Appoxo@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      Luckily I am using only traefik and everything goes through it that it needs for.
      Can’t imagine how annoying it would be to interface with every equipment so there are no https errors…