Comment on Decreasing Certificate Lifetimes to 45 Days

• helix@feddit.org ⁨2⁩ ⁨weeks⁩ ago

  most trouble is probably caused in the first few days. Doesn’t matter if it’s 45 or 90 days, it would have to be a few hours to be meaningfully short. Given that automating things like this is annoying sometimes, you’ll be sure people will max out the 45 days…

  I’m pretty sure it’s the SSL seller lobby just wanting more money, tbh. Selling snake oil security.

  source

  • Passerby6497@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    Given that automating things like this is annoying sometimes, you’ll be sure people will max out the 45 days…

    I know from professional experience that this is a stupid as fuck idea that leads to outages. One of the many reasons I’m working to automate those annoying ones.

    source

    • helix@feddit.org ⁨2⁩ ⁨weeks⁩ ago

      I’m not a capitalist, I don’t care about outages. I can live with Facebook being down for a few days, or my bank not accepting transfers for a day or so. Then again, I grew up with the internet in the 90s and prioritise good software and tools over availability, I guess?

      Obviously at my job I have to do what my employer thinks. But if nobody cared I’d definitely do our Gitlab upgrades once a week once they’re out and not in some weird “maintenance window” mandated by SLAs and stakeholders.

      source
  • mbirth@lemmy.ml ⁨2⁩ ⁨weeks⁩ ago

    I’m pretty sure it’s the SSL seller lobby just wanting more money, tbh. Selling snake oil security.

    And selling “certificate automation” tools.

    source

    • synae@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago

      it’s free

      source

      • mbirth@lemmy.ml ⁨2⁩ ⁨weeks⁩ ago

        Let’s Encrypt is. But tools to keep 100s of certificates up to date sometimes are not.

        source
  • False@lemmy.world ⁨2⁩ ⁨weeks⁩ ago

    Yeah you can still do a lot of damage in a few hours, but 45 days is a meaningful reduction in exposure time from year+

    source