Selfhosted

40296 readers

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

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

internal certificate distribution? (lemmy.world)

submitted 1 month ago by r0ertel@lemmy.world to c/selfhosted@lemmy.world

23 comments fedilink hide all child comments

How do you manage the distribution of internal TLS network certificates? I'm using cert-manager to generate them, but the root self-signed certificate expires monthly which makes distribution to devices outside of K8s a challenge. It's a PITA to keep doing this for the tablet, laptop and phones. I can bump the root cert to a year, but I'm concerned that the date will sneak up on me. Are there any automated solutions?

you are viewing a single comment's thread
view the rest of the comments

[–] vext01@lemmy.sdf.org 6 points 1 month ago (2 children)

I looked into this recently.

There's a DNS challenge designed for this exact scenario called (from memory) DNS01, but it's more of a faff than I'm willing to get involved with.

Basically you push proof that you own the domain into a DNS record instead of to a file on a web server. It requires a DNS provider that has an API and a client that speaks that API.

It also leaks private DNS stuff into the public domain.

I'd love it if someone devised an easier way. Maybe there is an easier way?

[–] eskuero@lemmy.fromshado.ws 5 points 1 month ago (2 children)

I do the dns challenge with letsencrypt too but to not leak local dns names into the public I just run a pihole locally that can resolve those domains

[–] skilltheamps 3 points 1 month ago* (last edited 1 month ago) (1 children)

The DNS server is only one thing you tell the domain, the other is the certificate authority. And those publish all issued certificates as part of certificate transparency. https://en.m.wikipedia.org/wiki/Certificate_Transparency

To mitigate the amount of published information, you can request wildcard certs to keep the subdomains private.

You can also use a wildcard cname entry to capture all subdomains and leave out the pihole faff, given that you use a reverse proxy that forwards to respective services by subdomain.

[–] eskuero@lemmy.fromshado.ws 1 points 1 month ago

Yep I also run wildcard domains for simplicity

[–] narc0tic_bird@lemm.ee 1 points 1 month ago

This is the way.

[–] fine_sandy_bottom@lemmy.federate.cc 1 points 1 month ago

This is me.

In public dns, configure *.home.example.com as an A record pointing to the local IP for my traefik container.

Traefik then manages all certificates. It sets a TXT record with my dns providers API like privatesercice.home.lebowheatcroft.com, requests the cert from letsencrypt, then deletes that TXT record.

Yes the local IP of my server is leaked, but names of services are not.