Comment on ICANN approves use of .internal domain for your network
vzq@lemmy.blahaj.zone 1 month agoWhy?
That’s a rather absolutist claim when you don’t know the orgs threat model.
Comment on ICANN approves use of .internal domain for your network
vzq@lemmy.blahaj.zone 1 month agoWhy?
That’s a rather absolutist claim when you don’t know the orgs threat model.
BestBouclettes@jlai.lu 1 month ago
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.
atzanteol@sh.itjust.works 1 month ago
No worse than protecting your ssh key. Just keep it somewhere safe.
Petter1@lemm.ee 1 month ago
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.
BestBouclettes@jlai.lu 1 month ago
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.
prime_number_314159@lemmy.world 1 month ago
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.