this post was submitted on 02 Dec 2025
459 points (99.1% liked)

Selfhosted

53502 readers
541 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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
[–] Valmond@lemmy.world 11 points 6 days ago* (last edited 5 days ago) (19 children)

And you still can't self certify.

It's cute the big players are so concerned with my little security of my little home server.

Or is there a bigger plan behind all this? Like pay more often, lock in to government controlled certs (already done I guess because they control DNS and you must have a "real" website name to get a free cert)?

I feel it's 50% security 50% bullshit.

Edit: thank you all I will dive down the CA certification rabbit hole now! Have worked in C++ & X509 on the client side so maybe I'll be able to figure it out.

[–] farcaller@fstab.sh 24 points 6 days ago (14 children)

You can absolutely run your own CA and even get your friends to trust it.

[–] Valmond@lemmy.world 1 points 6 days ago (7 children)

But you have to manually accept this dangerous cert in the browser right?

Very interesting actually, do you have any experience about it or other pointers? I might just set one up myself for my tenfingers sharing protocol...

[–] helios@social.ggbox.fr 2 points 6 days ago

No that's the point. If you import the CA certificate on your browser, any website that uses a cert that was signed by that CA will be trusted and accessible without warning.

load more comments (6 replies)
load more comments (12 replies)
load more comments (16 replies)