Technology

59374 readers

3671 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

192

Sysadmins slam Apple’s SSL/TLS cert lifespan cuts (www.theregister.com)

submitted 1 month ago by [email protected] to c/[email protected]

82 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 11 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Just going to mention my zero-dependency ACME (Let's Encrypt) library: https://github.com/clshortfuse/acmejs

It runs on Chrome, Safari, FireFox, Deno, and NodeJS.

I use it to spin up my wildcard and HTTP certificates. I've personally automated it by having the certificate upload to S3 buckets and AWS Certificates. I wrote a helper for Name.com for DNS validation. For HTTP validation, I use HTTP PUT.

[–] [email protected] 7 points 4 weeks ago (1 children)

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

[–] [email protected] 1 points 4 weeks ago (1 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.

[–] [email protected] 1 points 4 weeks ago (1 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).

[–] [email protected] 1 points 4 weeks ago (1 children)

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.

[–] [email protected] 1 points 4 weeks ago

Any machine I'm on has Python installed, so that's my go-to.