this post was submitted on 08 Aug 2024
499 points (99.2% liked)

Selfhosted

39435 readers
6 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 3 months ago (1 children)

Why?

That’s a rather absolutist claim when you don’t know the orgs threat model.

[–] [email protected] -3 points 3 months ago (2 children)

For self hosting at least, having your own CA is a pain in the ass to make sure everything is safe and that nobody except you has access to your CA root key.
I'm not saying it's not doable, but it's definitely a lot of work and potentially a big security risk if you're not 100% certain of what you're doing.

[–] [email protected] 8 points 3 months ago

No worse than protecting your ssh key. Just keep it somewhere safe.

[–] [email protected] 1 points 3 months ago (1 children)

Just use only VPN to access your services behind the reverse proxy, if you want prevent unauthorised connections.

CA certificates are not here to prevent someone accessing a site, they are here, so that you can be sure, that the server you are talking to is really the one belonging to the domain you entered and to establish a tunnel in order to send the API calls (html, css, javascript etc.) and answers encrypted.

[–] [email protected] 1 points 3 months ago (1 children)

That's the problem, if anyone somehow gets your root CA key, your encryption is pretty much gone and they can sign whatever they want with your CA.
It's a lot of work to make sure it's safe in a home setup.

[–] [email protected] 6 points 3 months ago (1 children)

You can just issue new certificates one per year, and otherwise keep your personal root CA encrypted. If someone is into your system to the point they can get the key as you use it, there are bigger things to worry about than them impersonating your own services to you.

[–] [email protected] 2 points 3 months ago

And additionally, you can sign intermediate Certificates reducing the risk even more, since you can revoke and re-issue new ones any time.