455

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
[-] farcaller@fstab.sh 25 points 6 days ago

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

[-] CosmicTurtle0@lemmy.dbzer0.com 14 points 6 days ago

Yes you can but the practicality of doing so is very limiting. Hell I ran my own CA for my own internal use and even I found it annoying.

The entire CA ecosystem is terrible and only exists to ensure connections are encrypted at this point. There's no validation or any sort of authority to say one site is better than another.

[-] fxdave@lemmy.ml 5 points 6 days ago

not all phones support manually adding certs

[-] False@lemmy.world 5 points 6 days ago

That's a complaint about those phones not PKI in general then. Though it's surprising their enterprise support won't let you since that is (or was) a fairly common thing for businesses to do.

[-] fxdave@lemmy.ml 2 points 6 days ago

That's a fair point. However, on the practical side, it's sad that I would have to root my gf's phone to let her access the services we host.

I ended up using a DynDNS and Caddy for managing my cert.

[-] Valmond@lemmy.world 2 points 6 days ago

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

[-] IsoKiero@sopuli.xyz 4 points 6 days ago

It's pretty simple to set up. Generate CA, keep key and other private stuff stored securely, distribute public part of CA to whoever you want and sign all the things you wish with your very own CA. There's loads of howtos and tools around to accomplish that. The tricky part is that manual work is needed to add that CA to every device you want to trust your certificates.

[-] Valmond@lemmy.world 1 points 5 days ago

Thank you! This is actually precisely what I need, you IT guys are the best!

[-] helios@social.ggbox.fr 3 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.

this post was submitted on 02 Dec 2025
455 points (100.0% liked)

Selfhosted

53454 readers
380 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