Selfhosted

53386 readers

124 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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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

454

Decreasing Certificate Lifetimes to 45 Days (letsencrypt.org)

submitted 4 days ago by artiman@piefed.social to c/selfhosted@lemmy.world

195 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

[–] cron@feddit.org 18 points 4 days ago (6 children)

The only disadvantage I see is that all my personal subdomains (e.g. immich.name.com and jellyfin) are forever stored in a public location. I wouldn't call it a privacy nightmare, yet it isn't optimal.

There are two workarounds:

do not use public certificates
use wildcard certificates only

[–] Burnoutdv@feddit.org 3 points 4 days ago (5 children)

But how to automate wildcard certificate generation? That requires a change of the txt record and namecheap for instance got no mechanism for that to automatically happen on cert bot action

[–] clif@lemmy.world 1 points 3 days ago (2 children)

Doesn't caddy support that (name cheap txt mod) via a plug-in?

I haven't tried it yet, but the plugin made it sound possible. I'm planning to automate on next expiration... When I get to it ;)

I did already compile caddy with the plugin, just haven't generated my name cheap token and tested.

[–] Burnoutdv@feddit.org 2 points 3 days ago (1 children)

"when i get to it" is my time frame aswell, till then its a reoccurring calendar notification with instructions because past me who set this all up was a genius compared to sleep deprived current me

[–] clif@lemmy.world 2 points 3 days ago* (last edited 3 days ago)

I definitely know that feeling.

Now that I'm at a keyboard, here's the (Caddy) plugin I was referring to : https://github.com/caddy-dns/namecheap

load more comments (2 replies)