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.

  • atzanteol@sh.itjust.worksEnglish
    1·
    1 day ago

    They’re cheap. You can also generate your own certs and use your own ca. But otherwise yes - quit yer bitching and learn how to do things right.

    • WhyJiffie@sh.itjust.worksEnglish
      1·
      22 hours ago

      You can also generate your own certs and use your own ca.

      I do this, with a custom root cert, but it has problems. some apps don’t accept it, some only accept it by totally disabling cert verification.

      installation is also very cumbersome: you go to a weird, badly structured menu on your phone deep in the settings, and select the certificate from storage where apps could have had replaced it while you were navigating the menu.
      it does not ask you for confirmation, does not show anything important about the cert, like its fingerprint you could use to quickly check its not been modified, any name constraints, validity period, etc. users cannot tell what that cert will grant its creator, because the system does not tell them anything so that they could decide, other than a generic “your connection may be monitored” message at all times. and when they refuse to install your cert, they are right, because this way it is very risky.

      so please tell me “how to do things right”, or shut up if you can’t tell any useful info

      • atzanteol@sh.itjust.worksEnglish
        1·
        4 hours ago

        so please tell me “how to do things right”, or shut up if you can’t tell any useful info

        WTF? I’m not trying to tell you how to do anything. I’m sick of selfhosted twerps bitching about “how hard it is to self host” when they think everything should be like an app on their phone. You need to learn how networks, dhcp, dns, ssl, certificates, etc. work.

        • WhyJiffie@sh.itjust.worksEnglish
          1·
          1 hour ago

          guess what, I know how these work. running 2 dozens of services over two machines, and as I said above, I use my own root certificate… that’s how I know that lots of apps have problems of varying severity with custom root certs! usage of user-installed certs is opt-in nowadays for smartphone apps, it’s not at all like on windows or linux.

          you are telling how to do things. the whole thread has been about you telling us to rent a domain for certificates and stop complaining about it being the only viable way…