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

Selfhosted

53304 readers
198 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
[–] farcaller@fstab.sh 24 points 3 days ago (3 children)

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

[–] CosmicTurtle0@lemmy.dbzer0.com 15 points 3 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.

[–] Valmond@lemmy.world 1 points 3 days ago (3 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...

[–] Unforeseen@sh.itjust.works 16 points 3 days ago (1 children)

No, because it's no longer dangerous if it's trusted.

You give your friends your public root and if applicable, intermediary certs. They install them and they now trust any certs issued by your CA.

Source: I regularly build and deploy CA's in corps

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

Thank you!

Is there some simple soft that let you make those certs, like with a root cert and then "derived" certs? On linux :-) ?

I guess people have to re-trust every now and then because certs get old, or do they trust the (public partof the) root cert and the daughter certs derived from root are churned out regularly for the sites?

[–] Unforeseen@sh.itjust.works 3 points 2 days ago (1 children)

Openssl can do everything.

That's right, but instead of the word derived we use "issued"

Correct certs get old by design, they can also be revoked. As another commenter mentioned the biggest pain is actually in the redistribution of these end certificates. In enterprise this is all managed usually with the same software they use for deployment or have auto enrollment configured.

You should find tons of guides just take it slow to understand it all. Understanding certificates in depth is a rare and good skill to have. Most sysadmins I come across are scared to death of certificates.

[–] Valmond@lemmy.world 1 points 1 day ago

I was forced to learn some of it at work (using and signing medical payment transactions, with x509 certificates) so I have ar least a starting point. I have no idea how the revoke process works though, I can't figure out a way that it functions without a central authority getting queried regularly. I thonk I can start without that knowledge though.

Anyway, with your information I'm up and running, thank you again!

"Derived certificates" not child certs, noted !

[–] IsoKiero@sopuli.xyz 4 points 3 days ago (1 children)

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 2 days ago

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

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

[–] fxdave@lemmy.ml 1 points 3 days ago (2 children)

not all phones support manually adding certs

[–] Auli@lemmy.ca 6 points 3 days ago (1 children)

Which phones. Android and iOS could.

[–] fxdave@lemmy.ml 4 points 3 days ago

I don't know about iOS, but Android had support for this in the past. Now the support is partial. It's no longer possible to install system-level certificates. Or at least they made it extremely inconvenient.

[–] False@lemmy.world 5 points 3 days ago (1 children)

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