Comment on Best way to get IPv4 connectivity to my self-hosted services
2xsaiko@discuss.tchncs.de 1 day ago
Yes, you can just use a reverse proxy for IPv4 only and point it to the IPv6 upstream. That is what I do, with a separate DNS record which then combines the two. See the DNS records for id.knifepoint.net (CNAME), http.vineta.knifepoint.net (AAAA, A) and vineta.knifepoint.net (AAAA).
rirus@feddit.org 1 day ago
But having a reverse proxy would enable someone getting access to it to read traffic, while having a VPN Tunnel won’t.
2xsaiko@discuss.tchncs.de 1 day ago
If someone manages to get root (!) access on this VPS it’s over either way.
gray@pawb.social 1 day ago
Your reverse proxy should have a cert with HTTPS.
2xsaiko@discuss.tchncs.de 1 day ago
Tbf, technically data is still decrypted at the reverse proxy and then re-encrypted. So if someone manages to reconfigure the proxy or read its memory somehow they could read traffic in plain text.
However then since they have to control the VPS, they could also get a new cert for that domain (at least the way I’ve configured it) even if it was passed as is to the real host via a tunnel and read the plaintext data that way, so I don’t think a tunnel protects against anything.
hank_and_deans@lemmy.ca 1 day ago
Or just use Nginx stream proxy, and all the encryption happens on the endpoints. No need for certs on the proxy at all.
This is how I make https and mqtts available on ipv4.
amdim@lemmy.dbzer0.com 1 day ago
I use this setup and don’t terminate SSL at the VPS and solely tunnel the encrypted traffic over a wire guard tunnel to the home lab where SSL is terminated.
The VPS solely serves to move the traffic from an external IP to an internal one.
It’s possible that someone could log into my server, change the nginx config to terminate SSL and then siphon data but it would take a few steps and can be somewhat mitigated by stapling the SSL certs that should be seen from the homelab.