Some services run really good behind a reverse proxy on 443, but some others can really become an hassle… And sometimes just opening other ports would be easier than to try configuring everything to work through 443.

An example that comes to my mind is SSH, yeah you can use SSLH to forward requests coming from 443 to 22, but it’s so much easier to just leave 22 open…

Now, for SSH, if you have certificate authentication or a strong password, I think you can feel quite safe, but what about other random ports? What risks I’m exposing my server to if I open some of them when needed for a service? Is the effort of trying to pass everything through 443/80 worth it?

  • Technus@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    15 hours ago

    If someone’s self-hosting, I’d be willing to bet they don’t have the same hardened config or isolation that a cloud provider would.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 hours ago

      Docker restricts the permissions of software running in the container. It is hardened by default and you need to manually grant permissions in some rare cases.