• Shirasho@lemmings.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 days ago

    This is a surprisingly common issue. I’ve had it happen at least once in every job I’ve worked. This is usually the responsibility of the devops or devsec teams, and they are usually heavily underfunded since they are cost centers that do not bring in profit.

    • ZeDoTelhado@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      There are tools to actually remind you to do this on a timely fashion… Also, some of them go as far as doing auto renewal. Is this such a hard thing?

    • AudaciousArmadillo@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      I’m young enough that I never had to experience anything but let’s encrypt/ACME. Manually renewing certs sounds like such a major PITA that I’d switch to it as soon as I could…

    • AmbiguousProps@lemmy.today
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      11 days ago

      I work in DevOps, this is one of the easier things to automate. It’s common for certs to be issued on a 90 day basis these days, no way that would be maintainable without automating.

      • The issue here is this is a client certificate, issued within the League client, for seemingly local<->local traffic. This ain’t no typical HTTPS ceritifcate, it’s bundled into the client build. See from the source “League client’s hard-coded certificate meant someone at Riot would’ve needed to remember it required updating before its expiration date.” So, not quite as easy as configuring an ACME CRON, but something that’d need to be remembered or have some kind of internal reminder for.

        • AmbiguousProps@lemmy.today
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 days ago

          I’m aware, but it should have been part of their build system and they should have, at the very least, had alarms for this.

        • dgdft@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          11 days ago

          Have you had Certbot or LE fail on prod for you before?

          I’m sure stuff happens, but I usually view them as one of the most robust moving parts on a server.

          E: I don’t mean to express disbelief at all; just curious to learn about possible footguns.

          • four@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 days ago

            Certbot / LE has to be running on some machine and that machine can be accidentally turned off, payments not fulfilled, was supposed to be moved but the new instance doesn’t work, gateway configuration changed, etc.

            Automation requires maintenance and that introduces human error