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:

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

458

Decreasing Certificate Lifetimes to 45 Days (letsencrypt.org)

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

192 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

[–] bss03@infosec.pub 4 points 2 days ago (2 children)

Technically my renews aren't automated. I have a nightly cronjob that should renew certificates and restart services, but when the certificates need renewal, it always fails because it wants to open a port I'm already using in order to answer the challenge.

I hear there's an apache module / configuration I can use, but I never got around to setting it up. So, when the cron job fails, I get an email and go run a script that stops apache, renews certs, and restarts services (including apache). I will be a bit annoying to have to do that more often, but maybe it'll help motivate me to configure apache (or whatever) correctly.

Debian Stable

[–] eclipse@lemmy.world 12 points 2 days ago (1 children)

You could try using the DNS challenge instead; I find it a lot more convenient as not all my services are exposed.

[–] bss03@infosec.pub 1 points 2 days ago* (last edited 2 days ago)

While I do have some control over my DNS and can create arbitrary TXT entries, I can't to that in an automated way easily. I'm using Gandi.net to host my DNS rather than running my own DNS sever(s).

EDIT: Gandi is listed https://community.letsencrypt.org/t/dns-providers-who-easily-integrate-with-lets-encrypt-dns-validation/86438 so maybe I can automate a DNS-01 challenge without too much issue, I just have to switch away from certbot to one of the other tools.

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

The usual way for me is to give certbot write access to a directory in the HTTP root, so the server can keep running.

[–] bss03@infosec.pub 2 points 2 days ago* (last edited 2 days ago)

It does have access to the HTTP root directories. But, it still can't open port 80/443 when apache already has that port open.

EDIT: I guess my certbot renew just needs to be reconfigured to use a --webroot, so it doesn't try to listen on it's own.