• sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    14
    ·
    3 months ago

    Interesting. I use LetsEncrypt largely for internal services, of which I expose a handful externally, and I’ve been thinking of only opening the external port mapping for cert renewals. With this at 90 days, I was planning on doing this once/month or so, but maybe I’ll just go script it and try doing it every 2-3 days (and only leave the external ports open for the duration of the challenge/response).

    I’m guessing my use-case is pretty abnormal, but it would be super cool if they had support for this use-case. I basically just want my router to handle static routes and have everything be E2EE even on my LAN. Shortening to 6 days is cool from a security standpoint, but a bit annoying for this use-case.

    • Kurt@lemm.ee
      link
      fedilink
      English
      arrow-up
      31
      ·
      3 months ago

      You can use DNS challenge to renew your certificates without opening ports! Have a look at acme.sh for automation.

      • sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        7
        ·
        edit-2
        3 months ago

        Oh, awesome! I thought that was a manual process, so I’ve been using the regular method.

        Looks like I have a new project for this weekend. My DNS is currently hosted at Cloudflare, so this should be pretty straightforward.