From today until March 15, 2026, the maximum lifetime for a TLS certificate is 398 days.

As of March 15, 2026, the maximum lifetime for a TLS certificate will be 200 days.

As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.

As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.

What’s everyone’s opinion on this? I think from a security standpoint their reasoning is valid and in many cases it’s very easy to automate the renewal with ACME or something else. But there’s likely gonna be legacy stuff still around in 2029 that won’t be easy to automate.

  • Z3k3@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    My little corner of the business has started migrating our certs to let’s encrypt.

    Hope it catches on else where

  • nazgul666@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    If I understand this correctly, it only affects certificates issued by public CAs (certificates for public websites, for example). So for certs issued by a company CA (e.g. for internal infrastructure), it should not apply. Can anyone confirm?

    • prime_number_314159@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      The browser warning appears even for a cert issued by a non public CA you have told your browser to trust, and most browsers already enforce a 398 day limit, so unless you have cooperative users, you’re already (effectively) capped at 1 year of validity.

      • lud@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        No, that’s fortunately not correct. TLS certificates issued by our CA are valid for 2 years and that works perfectly fine in all the browsers I have ever used.

  • SkaveRat@discuss.tchncs.de
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Doesn’t really affet me much, as my LE cronjob will update the cert either way. Doesn’t really matter if it’s 90 days or 47 (what a weird number of days)

    • ShortN0te@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I only can assume: 1.5 months rounded up, using 31 days a month 31+16=47

      So you get half a month to realize that your monthly automated renewal is broken?

  • reisub@discuss.tchncs.de
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I like it. This action is inevitable in my opinion, and there will always be legacy systems regardless of the timeline, better start sooner than later.