Hello,

I stopped using TeamViewer a very long time ago. Since then, I’ve been using DWService and I’m quite happy with it. I like the fact that I can access to the terminal without launching any graphical component on the machine (which is handy for my headless servers, and allows me not to open SSH port). I also like the fact that it works even if my VPN server is down, as I can access remote servers that aren’t accessible via the web when they’re no longer reachable through my VPN.

However, there are a few issues that are bothering me more and more. I’ve switched my mum’s computer to Fedora and, whilst it worked perfectly under Windows, remote control is very buggy under fedora because the connection isn’t great. Furthermore, it’s impossible to access the screen if the computer isn’t unlocked.

So, I’d really like to find a solution that meets my criteria:

  • Accessible via a web browser
  • Ideally open-source
  • Free
  • Ideally self-hostable, but I’m worried that if, for example, my reverse proxy or VPN crashes, I won’t be able to access my machines to debug them?
  • Allows access to servers without a monitor
  • Allows access to computers running Fedora without the need for prior unlocking

Thanks!

  • 7EP6vuI@feddit.orgEnglish
    1·
    2 days ago

    why don’t you want to open an ssh port? what’s wrong with that?

    just disable password authentication, and maybe get fail2ban. am i missing something?

    • neidu4@piefed.socialEnglish
      2·
      2 days ago

      Optional extra, which I do: Change the SSH port to something non-standard. It’s not more secure, but it does cut down on the logspam.

      • nibbler@discuss.tchncs.deEnglish
        1·
        1 day ago

        I’d argue it’s even more secure, as it reduces the amount of attacks you are exposed to. For targeted attacks it changes absolutely nothing. But it keeps you our of a few DBs and spares some brute force attacks.

      • lntl@lemmy.mlEnglish
        2·
        1 day ago

        IMO ssh is the tool you’re describing. My ssh server is exposed to the WAN and is configured like this:

        • set to a random port to reduce spam (completely eliminated it for me)
        • set PasswordAuthentication no
        • set PermitRootLogin no
          • lntl@lemmy.mlEnglish
            2·
            1 day ago

            root is a user account that has all privileges and is what bots are programmed to probe, so exposing it introduces unnecessary risk. IMO there’s no reason to permit root login via ssh in any circumstance, ever, in all cases, absolutely.

            For all the people thinking, “well the world doesn’t work in absolutes, there’s always a special case!” There isn’t.

            If a user needs to use elevated permissions, there are many ways to do that without exposing root. sudo(8) is one way to do that.

            • DougPiranha42@lemmy.worldEnglish
              1·
              1 day ago

              Thanks for the great explanation! Seems like because logging in as root is never necessary and indeed never done; people confuse sudoer for root login.

          • Guiorgy@lemmy.mlEnglish
            0·
            1 day ago

            Without root user login, the attacker would have to guess not only the password to the user but also the username (hopefully it’s not something simple like admin), and once you are logged in you can use sudo -i to chage into root, which will require a password, therefore, we also disable password login so if someone does manage to somehow compromise the SSH user, they’d still need the password to become root.

            • 7EP6vuI@feddit.orgEnglish
              1·
              9 hours ago

              guess not only the password

              what password? shouldn’t we all use ssh-keys by now?