192
Sysadmins slam Apple’s SSL/TLS cert lifespan cuts (www.theregister.com)
submitted 2 years ago by to c/technology@lemmy.world
81 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 2 years ago (4 children)

Why have this run in the browser? Why not just have it run on the server and renew in the background?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 years ago (3 children)

    That's what NodeJS and Deno are.

    The point of the browser support means it runs on modern Web technologies and doesn't need external binaries (eg: OpenSSL). It can literally run on any JS, even a browser.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 years ago (2 children)

    I'm aware, but you led with Chrome, Safari, and Firefox, so it sounded like browser support was the point, so I was curious what the use-case was.

    That's still cool though. I personally would've just use Python, since that's generally available everywhere I'd want to run something like this (though Python's built-in HTTP lib isn't nearly as nice as JS's fetch(), I'd want requests).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    I have just dumped code into a Chrome console and saved a cert while in a pinch. It's not best practices of course, but when you need something fast for one-time use, it's nice to have something immediately available.

    You could make your own webpage that works in the browser (no backend) and make a cert. I haven't published anything publicly because you really shouldn't dump private keys in unknown websites, but nothing is stopping you from making your own.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •