Comment on Best way to get IPv4 connectivity to my self-hosted services

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

  source

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

    source

    • 2xsaiko@discuss.tchncs.de ⁨1⁩ ⁨day⁩ ago

      Oh interesting, I’ll have to look into that. Is this with that “proxy protocol” I’ve seen mentioned? If not, does this preserve it pass through the client socket address?

      source

      • hank_and_deans@lemmy.ca ⁨22⁩ ⁨hours⁩ ago

        It’s merely a tcp proxy. It doesn’t even have to be http since it has no idea. The trick with tls is that it can extract the requested host name via SNI.

        source

        • -> View More Comments
  • 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.

    source