Comment on TLS Certificate Lifetimes Will Officially Reduce to 47 Days

dan1101@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

• Rogue@feddit.uk ⁨3⁩ ⁨weeks⁩ ago

  If you’re truly unaware of why TLS is necessary or how to automate the process then you should probably retire.

  Archaic attitudes like yours are precisely why these restrictions are necessary.

  source

  • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

    Exactly. Setting up Let’s Encrypt is really easy, and once it’s set up, you don’t have to think about it.

    I did it for self-hosted stuff, and it’s trivial. You can even do DNS challenge auth instead of HTTP and you don’t need to have port 80 open at all, but you do need a login token for your DNS host for the script.

    The first one will probably take an hour or two if it’s your first time, and after that, it’s maybe 5 min per site.

    source

    • paraphrand@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Exactly. Setting up Let’s Encrypt is really easy, and once it’s set up, you don’t have to think about it.

      That’s what I thought. And now I need to figure out how to update it for 47 day cycles.

      source

      • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

        I have mine check daily, which is the default and is recommended. It only actually updates when it’s close to renewal, so I never need to care how short the renewal period is.

        source
    • rbos@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

      Not all DNS hosts support that. Webnames.ca, looking at you…

      Also my workplace hosts their own dns and I think it will be a cold day in hell before they let me do automated updates.

      source

      • exu@feditown.com ⁨3⁩ ⁨weeks⁩ ago

        Any DNS host that doesn’t support automation either starts building now or goes out of business when short certs are implemented.

        source
      • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

        Sure, but it’s really nice if it does.

        I use Cloudflare, and my login token only supports editing DNS records, which is nice. If yours doesn’t, it may be worth switching to one that does. There are lots of options and many of them have a reasonable API.

        source
      • corsicanguppy@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

        Also my workplace hosts their own dns

        The best way to control the data.

        and I think it will be a cold day in hell before they let me do automated updates.

        This is of waning value, but don’t jump into half-assed automation early or you end up with problems like route53 hijacking.

        source
    • Rogue@feddit.uk ⁨3⁩ ⁨weeks⁩ ago

      Even that’s more steps than necessary.

      Just serve your website with Caddy and it handles certs for you. The config is absolutely trivial compared to Apache, nginx, etc

      source

      • corsicanguppy@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

        Just

        Red flag.

        serve your website with Caddy

        There is no security risk so bad that it can’t be made worse by layering on new tech with its own issues and pitfalls. (Paraphrasing Bruce Jackson)

        source
      • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

        I use Caddy, but there are a lot of options with decent documentation.

        source
  • corsicanguppy@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

    If you’re truly unaware of why TLS is necessary or how to automate the process then you should probably retire.

    Oof. You’re gonna hit the bottom of the table with your knee like that.

    What part of your security training skipped over understanding the customer’s setup before making recommendations?

    source