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.

  • Valmond@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    3
    ·
    2 hours ago

    And you still can’t self certify.

    It’s cute the big players are so concerned with my little security of my little home server.

    Or is there a bigger plan behind all this? Like pay more often, lock in to government controlled certs (already done I guess because they control DNS and you must have a “real” website name to get a free cert)?

    I feel it’s 50% security 50% bullshit.

      • Valmond@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        But you have to manually accept this dangerous cert in the browser right?

        Very interesting actually, do you have any experience about it or other pointers? I might just set one up myself for my tenfingers sharing protocol

        • Unforeseen@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          4
          ·
          19 minutes ago

          No, because it’s no longer dangerous if it’s trusted.

          You give your friends your public root and if applicable, intermediary certs. They install them and they now trust any certs issued by your CA.

          Source: I regularly build and deploy CA’s in corps

        • ℍ𝕖𝕝𝕚0𝕤@social.ggbox.fr
          link
          fedilink
          English
          arrow-up
          1
          ·
          13 minutes ago

          No that’s the point. If you import the CA certificate on your browser, any website that uses a cert that was signed by that CA will be trusted and accessible without warning.

    • stratself@lemdro.id
      link
      fedilink
      English
      arrow-up
      1
      ·
      57 minutes ago

      Technically something like DANE can allow you to present DNSSEC-backed self-signed certs and even allow multi-domain matching that removes the need for SNI and Encrypted Client Hello… but until the browsers say it is supported, it’s not