• solrize@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 hours ago

    Lame. 45 days? 10 days for DCV? How common are exploits involving old certificates anyway? And automated cert management is just another exploit target. Do they seriously think an attacker who pwns a server can’t keep the automatic renewals running?

    • 0x0@programming.dev
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      4 hours ago

      The solution, according to Sectigo’s Chief Compliance Officer Tim Callan, is to automate certificate management — unsurprising considering the firm sells software that does just this.

  • fartsparkles@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    3
    ·
    4 hours ago

    Smells like Apple knows something but can’t say anything. What reason would they want lifespans cut so short other than they know of an attack vector that means more than 10 days isn’t safe?

    AFAIK they’re not a CA that sells certs so this can’t be some money making scheme. And they’ll be very aware how unpopular 10 day lifespans would be to services that suck and require manual download and upload every time you renew.

    • 0x0@programming.dev
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      7
      ·
      4 hours ago

      Smells like you didn’t read the article, it’s an ongoing trend:

      Max lifespans of certs have been gradually decreasing over the years in an ongoing effort to boost internet security. Prior to 2011, they could last up to about eight years. As of 2020, it’s about 13 months.

      • fartsparkles@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        2 hours ago

        Thank you for the smug response however I did indeed read the article and going from 13 months to 10 days is not a trend but a complete rearchitecture of how certificates are managed.

        You have no idea how many orgs have to do this manually as their systems won’t enable it to be automated. Following a KBA once a year is fine for most (yet they still forget and websites break for a few days; this literally happened to NVD of all things a few weeks ago).

        This change is a 36x increase in effort with no consideration for those who can’t renew and apply certs programmatically / through automation.

      • li10@feddit.uk
        link
        fedilink
        English
        arrow-up
        16
        arrow-down
        1
        ·
        3 hours ago

        Reducing it to one year made sense, one year down to 10 days is actually a fucking massive difference. Practically speaking, it’s a far, far bigger change than 8 years down to 1.

        This isn’t just an “ongoing trend” at this point, it would be a fundamental change to the way that certificates are managed i.e. making it impossible to handle renewals manually for any decently sized business.

  • exu@feditown.com
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    12
    ·
    4 hours ago

    Good, certificates should be automated anyways. Much more reliable than the once yearly outages because nobody renewed the thing or forgot some systems.

    • 0x0@programming.dev
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      4 hours ago

      Good, certificates should be automated anyways.

      The problem being when that can’t be easily automated? Did you read the article?

      • Justin@lemmy.jlh.name
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        5
        ·
        3 hours ago

        They should be automated too.

        The fact that I can’t use terraform to automatically deploy certs to network appliances is a problem.

        • hemko@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          2 hours ago

          Technically, you shouldn’t even deploy certs to network appliances or servers but they should fetch certificates automatically from a vault. I know there’s minimal support for such things right now from some vendors, but that should be fixed by those vendors.

          Even Microsoft supports such solutions in Azure both with PaaS components and Windows and Linux servers (in Azure or onprem) via extensions

          • Justin@lemmy.jlh.name
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            1 hour ago

            True.

            cert-manager is an amazing tool for deploying certificates for containerized applications. There’s no standardized way to deploy those certs outside of containers without scripting it yourself though, unfortunately.

      • exu@feditown.com
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        7
        ·
        4 hours ago

        Good incentive for the provider to fix it or go out of business.