• thesmokingman@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    AWS makes this impossible in a few places such as a fair number of ACM use-cases.

    I think your cert-per-session idea is interesting. We’d need significant throughput and processing boosts to make that happen, probably at least on the order of 10X computing speeds and 10X transmission speeds across the board minimum. These operations are computationally intense and add data to the wire so, for example, a simple Lemmy server with hundreds of users slows to a crawl and a larger site eg Mastodon goes to dialup speeds or worse. You can test at home by trying to generate an x509 self-signed cert before connecting to a website every time.

    • Onno (VK6FLAB)@lemmy.radio
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Well AWS ACM already automates this, so if the renewal period gets shortened, I’m guessing that this will be updated to suit, unless I’m misunderstanding your point.

      I hadn’t considered the CPU load, but that’s a fair point. I’m guessing that a suitable piece of code will utilise specialised hardware, or perhaps leverage the GPU or just in time SSL certificates will become a thing.