Selfhosted

53285 readers

1038 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 posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

344

Decreasing Certificate Lifetimes to 45 Days (letsencrypt.org)

submitted 1 day ago by artiman@piefed.social to c/selfhosted@lemmy.world

123 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

[–] Zanathos@lemmy.world 1 points 9 hours ago (1 children)

While I agree for my personal use, it's not so easy in an enterprise environment. I'm currently working to get services migrated OFF my servers that utilize public certificates to avoid the headache of manual intervention every 45 days.

While this is possible for servers and services I manage, it's not so easy for other software stacks we have in our environment. Thankfully I don't manage them, but I'm sure I'll be pulled into them at some point or another to help figure out the best path forward.

The easy path is obviously a load balanced front-end to load the certificate, but many of these services are specialized and have very elaborate ways to bind certificates to services outside of IIS or Apache, which would need to trust the newly issued load balancer CA certificate every 47 days.

[–] fatalicus@lemmy.world 1 points 3 hours ago

Yeah, this has become an issue for us at work as well.

Currently we are doing a POC for an in-house developed solution where a azure function app handles the renewal of certificates for any domain we have, both wildcard and named, and place the certificates in a key vault where services that need them can get access.

Looks to be working, so the main issue now is finding a non-US certificate provider that supports acme. EU has some but even more local there aren't many options.