Hello selfhosters. I have a Linux VM spun up on my server that I access via Remmina. Would it be ok for me to expose Remmina for external access? It would be behind a reverse proxy as well as Authelia 2FA of course. Is that secure “enough”, just for a VM?

  • harrim4n@feddit.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    In the end it depends on your risk profile and adversary model. Usually it’s not a good idea though. Why not have an SSH tunnel to the network/machine and use port forwarding to forward the RDP connection? Or why not use SSH for remote access, period?

    • chandz05@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      My work’s network is pretty locked down, which is why I’m trying to think of other solutions that would work.

    • chandz05@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Hey man, so I’ve been thinking about this and doing a lot of reading since I read your comment… Question: what makes an SSH tunnel any more secure than an SSL connection through a browser? I only have port 443 opened on my home network for reverse proxy and wouldn’t want to open anything more to the internet. Am I missing something fundamental in terms of security? I would definitely like to understand this more.

      • dragnet@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        The nice thing about an SSH tunnel is that it only exists when you create it, on the fly, per use, with your SSH credentials. And it is only accessible if you possess an authorized private key. An SSL connection through a browser doesn’t fill the same role. SSL provides privacy and security in the communication between server and client. It doesnt have authentication built in. If you are accessing through a web browser you are probably talking to a web server, but SSH allows you to tunnel any protocol (web, rdp, whatever) forwarding traffic, encrypted, across a chosen port.

        Edit to add a bit more: attack surface. SSH is a very robust and heavily used protocol with well tested implementations. Other solutions involving the web are probably involving software stacks with layers of configuration, more rapid iteration to add features and therefore a higher probability of vulnerabilities existing or being introduced in updates. Is this consideration relevant to your use? Probably not, =P but you asked about what might differentiate these two approaches from a security standpoint.

        • chandz05@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Ah perfect! Exactly what I was looking for! Thank you so much for that explanation. Definitely trying to understand more about security and your explanation just made something click in my brain :)