Selfhosted

53360 readers

607 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

449

Decreasing Certificate Lifetimes to 45 Days (letsencrypt.org)

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

190 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

[–] WhyJiffie@sh.itjust.works 1 points 12 hours ago (1 children)

yes you need if you want HTTPS that is accepted by the smartphone client apps of your services.

domains are a constant expense

[–] atzanteol@sh.itjust.works 1 points 11 hours ago (1 children)

They're cheap. You can also generate your own certs and use your own ca. But otherwise yes - quit yer bitching and learn how to do things right.

[–] WhyJiffie@sh.itjust.works 1 points 1 hour ago

You can also generate your own certs and use your own ca.

I do this, with a custom root cert, but it has problems. some apps don't accept it, some only accept it by totally disabling cert verification.

installation is also very cumbersome: you go to a weird, badly structured menu on your phone deep in the settings, and select the certificate from storage where apps could have had replaced it while you were navigating the menu.
it does not ask you for confirmation, does not show anything important about the cert, like its fingerprint you could use to quickly check its not been modified, any name constraints, validity period, etc. users cannot tell what that cert will grant its creator, because the system does not tell them anything so that they could decide, other than a generic "your connection may be monitored" message at all times. and when they refuse to install your cert, they are right, because this way it is very risky.

so please tell me "how to do things right", or shut up if you can't tell any useful info