Comment on I’m looking for the best remote access solution that works for me

• lntl@lemmy.ml ⁨3⁩ ⁨weeks⁩ 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

  original

  • 7EP6vuI@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    why no root login? how do you become root if you need it?

    original

    • lntl@lemmy.ml ⁨3⁩ ⁨weeks⁩ ago

      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.

      original

      • DougPiranha42@lemmy.world ⁨3⁩ ⁨weeks⁩ 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.

        original
      • 7EP6vuI@feddit.org ⁨3⁩ ⁨weeks⁩ ago

        do you use sudo with a password? this and the unknown username is what get as additional security then?

        original
    • Guiorgy@lemmy.ml ⁨2⁩ ⁨weeks⁩ 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.

      original

      • 7EP6vuI@feddit.org ⁨2⁩ ⁨weeks⁩ ago

        guess not only the password

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

        original

        • -> View More Comments
    • lewy@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      sudo -i is what I would do or su root if your other user is not a superuser.

      original
• Guiorgy@lemmy.ml ⁨2⁩ ⁨weeks⁩ ago

  You could spin a publicly exposed WireGuard daemon firewalled to allow peers access to the non-public SSH port only, which would result in double encryption, but would give you the peace of mind that an attacker would have to compromise both at the same time, which is very unlikely. Plus, WireGuard is very cheap to deploy and produces no logs. We use that model in my office to access our server.

  original