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

Selfhosted

53285 readers
1038 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.

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 10 points 1 day ago* (last edited 1 hour ago) (3 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 22 points 1 day ago (2 children)

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

[–] CosmicTurtle0@lemmy.dbzer0.com 15 points 21 hours 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 1 day 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 13 points 23 hours 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 1 points 1 hour ago

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?

[–] IsoKiero@sopuli.xyz 3 points 21 hours 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 1 hour ago

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

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

[–] stratself@lemdro.id 6 points 23 hours ago (1 children)

Technically something like DANE can allow you to present DNSSEC-backed self-signed certs and even allow multi-domain matching that removes the need for SNI and Encrypted Client Hello... but until the browsers say it is supported, it's not

[–] RheumatoidArthritis@mander.xyz 2 points 17 hours ago

At some point there was a browser extension to support DANE (and Perspectives and similar approaches against centralization) but since then, browser vendors fixed that security flaw.

[–] Passerby6497@lemmy.world -1 points 20 hours ago* (last edited 20 hours ago) (1 children)

And you still ~~can't~~ can self certify.

Skill issue, you've always been able to self certify. You just have to know where to drop the self signed cert or the parent/root cert you use to sign stuff.

If you're running windows, it's trivial to make a self signed cert trusted. There's an entire certificate store you can access that makes it easy enough you can double click it and install it and be on your way. Haven't had a reason to figure it out on Linux, but I expect it won't be super difficult.

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

I already did but my browser choked on it.

So yes I should probably set up the whole CA thing.