• drspod@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    but maybe I’m missing something.

    Yes, FTA:

    May 13, 2026: the tlsclient ACME profile will no longer be available and no further certificates with the Client Authentication EKU will be issued.

    Once this is completed, Let’s Encrypt will switch to issuing with new intermediate Certificate Authorities which also do not contain the TLS Client Authentication EKU.

    After this change is complete, only TLS Server Authentication will be available from Let’s Encrypt.

    • just_another_person@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      Yes, that’s the same thing. Removing it from one place, and just adding it to another. No big deal.

      I honestly don’t think many people were even using this feature compared to SSL certs. Anyone using TLS everywhere already has their own cert manager workflow, othey’d be using another system to do it ala k8s, or they’d be doing it at the network fabric instead of per-service. I can’t think of many use-cases where regular users of LE would have a TLS-enabled public service they would need other random users to trust. I’m sure there’s some, but nowhere on the scale of their SSL users.

      • drspod@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        3 days ago

        Yes, that’s the same thing. Removing it from one place, and just adding it to another.

        Adding it where?