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

[–] atzanteol@sh.itjust.works 9 points 1 day ago (1 children)

It's being deiven by the browsers. Shorter certs mean less time for a compromised certificate to be causing trouble.

https://cabforum.org/working-groups/server/baseline-requirements/requirements/

[–] helix@feddit.org 1 points 1 day ago (2 children)

most trouble is probably caused in the first few days. Doesn't matter if it's 45 or 90 days, it would have to be a few hours to be meaningfully short. Given that automating things like this is annoying sometimes, you'll be sure people will max out the 45 days…

I'm pretty sure it's the SSL seller lobby just wanting more money, tbh. Selling snake oil security.

[–] Passerby6497@lemmy.world 1 points 20 hours ago* (last edited 20 hours ago) (1 children)

Given that automating things like this is annoying sometimes, you'll be sure people will max out the 45 days…

I know from professional experience that this is a stupid as fuck idea that leads to outages. One of the many reasons I'm working to automate those annoying ones.

Also, don't let perfect be the enemy of better.

[–] helix@feddit.org 0 points 11 hours ago

I'm not a capitalist, I don't care about outages. I can live with Facebook being down for a few days, or my bank not accepting transfers for a day or so. Then again, I grew up with the internet in the 90s and prioritise good software and tools over availability, I guess?

Obviously at my job I have to do what my employer thinks. But if nobody cared I'd definitely do our Gitlab upgrades once a week once they're out and not in some weird "maintenance window" mandated by SLAs and stakeholders.

[–] False@lemmy.world 1 points 22 hours ago

Yeah you can still do a lot of damage in a few hours, but 45 days is a meaningful reduction in exposure time from year+