this post was submitted on 02 Dec 2025
469 points (99.2% liked)
Selfhosted
59850 readers
724 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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/
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.
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.
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.
And selling “certificate automation” tools.
it's free
Let’s Encrypt is. But tools to keep 100s of certificates up to date sometimes are not.
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+