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.

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.worldEnglish
    1·
    7 小时前

    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.worksEnglish
      10·
      6 小时前

      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

    • IsoKiero@sopuli.xyzEnglish
      2·
      4 小时前

      It’s pretty simple to set up. Generate CA, keep key and other private stuff stored securely, distribute public part of CA to whoever you want and sign all the things you wish with your very own CA. There’s loads of howtos and tools around to accomplish that. The tricky part is that manual work is needed to add that CA to every device you want to trust your certificates.

    • ℍ𝕖𝕝𝕚0𝕤@social.ggbox.frEnglish
      2·
      6 小时前

      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.