Selfhosted

59897 readers

697 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

469

Decreasing Certificate Lifetimes to 45 Days (letsencrypt.org)

submitted 6 months ago by artiman@piefed.social to c/selfhosted@lemmy.world

196 comments fedilink hide all child comments

Let’s Encrypt will be reducing the validity period of the certificates we issue. We currently issue certificates valid for 90 days, which will be cut in half to 45 days by 2028.
This change is being made along with the rest of the industry, as required by the CA/Browser Forum Baseline Requirements, which set the technical requirements that we must follow. All publicly-trusted Certificate Authorities like Let’s Encrypt will be making similar changes. Reducing how long certificates are valid for helps improve the security of the internet, by limiting the scope of compromise, and making certificate revocation technologies more efficient.

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

[–] merc@sh.itjust.works 2 points 6 months ago (3 children)

I'm using automated renewals.

But, that just means there's a new cert file on disk. Now I have to convince a half a dozen different apps to properly reload that changed cert. That means fighting with Systemd. So Systemd has won the first few skirmishes, and I haven't had the time or energy to counterattack. Now instead of having to manually poke at it 4x per year, it's going to be closer to once a month. Ugh.

[–] nialv7@lemmy.world 5 points 6 months ago (1 children)

Half a dozen sounds like a lot, kinda curious what you are running? If they all are web services maybe use a reverse proxy or something?

[–] merc@sh.itjust.works 1 points 6 months ago (1 children)

Web services, and then various components of an email system.

[–] JadedBlueEyes@programming.dev 0 points 6 months ago (1 children)

If you have the time to set it up, Stalwart can manage its own cert renewal.

[–] merc@sh.itjust.works 1 points 6 months ago (1 children)

I don't want to have to completely redo my whole email stack.

[–] JadedBlueEyes@programming.dev 0 points 6 months ago

Which is fair enough

[–] eclipse@lemmy.world 1 points 6 months ago

You could try a path unit watching the cert directory (there are caveats around watching the symlinks directly) or most acme implementations have post renewal hooks you can use which would be more reliable.

[–] NotMyOldRedditName@lemmy.world -5 points 6 months ago* (last edited 6 months ago)

Don't worry, they'll sell you new software for another $50.00/m/certificate to help with the new certificate fiddling you now have to do monthly. It didn't make sense for them to release it until they pushed through the 45 day window change through backchannels.