Comment on How can I keep my forwarded port secure?

• teawrecks@sopuli.xyz ⁨1⁩ ⁨week⁩ ago

  Normal for who? I wouldn’t expose SSH on 22 to the internet unless you have someone whose full time job is monitoring it for security and keeping it up to date. There are a whole lotta downsides and virtually no upsides given that more secure alternatives have almost zero overhead.

  source

  • i_am_not_a_robot@discuss.tchncs.de ⁨1⁩ ⁨week⁩ ago

    Shodan reports that 35,780,216 hosts have SSH exposed to the internet.

    Moving SSH to ports other than 22 is not security. The bots trying port 22 on random addresses with random passwords don’t have a chance of getting in unless you’re using password authentication with weak passwords or your SSH is very old.

    SSH security updates are very infrequent and it takes practically no effort to keep SSH up to date. If you’re using a stable distribution, just enable automatic security updates.

    source

    • lud@lemm.ee ⁨1⁩ ⁨week⁩ ago

      Moving to another port isn’t a bad idea though. It gives you cleaner logs which is nice.

      source
    • JustEnoughDucks@feddit.nl ⁨1⁩ ⁨week⁩ ago

      To be fair, if something is open by default or very easy to enable without informing about the risks, tons of people will have it exposed without thinking.

      It isn’t that “tons of people do it so it is normal and perfectly fine” but more “people don’t realize.” It also uses some nontrivial amount of resources to process and block those attempts, even if they never have a chance of getting in.

      There is yet a reason I can find to have it forwarded for home use. Need to ssh into a machine to fix it? VPN.

      There are plenty of secure web-based tools to manage your server without a VPN also.

      source

      • i_am_not_a_robot@discuss.tchncs.de ⁨1⁩ ⁨week⁩ ago

        A large percentage of those hosts with SSH enabled are cloud machines because it’s standard for cloud machines to be only accessible by SSH by default. I’ve never seen a serious security guide that says to set up a VPN and move SSH behind the VPN, although some cloud instances are inherently like this because they’re on a virtual private network managed by the hosting provider for other reasons.

        SSH is much simpler and more universal than a VPN. You can often use SSH port forwarding to access services without configuring a VPN. Recommending everyone to set up a VPN for everything makes networking and remote access much more complicated for new users.

        source

        • -> View More Comments
  • keyez@lemmy.world ⁨1⁩ ⁨week⁩ ago

    I had it open for a web server for 2.5 years because I was lazy and my IP changed a lot and I traveled and didn’t have a VPN setup and never had any issues as far as I could tell. Disabled password and root auth but was also fine with wiping that server if there were issues. It’s certainly not recommended but isn’t immediately always going to be an issue

    source

    • atzanteol@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

      ssh is one of the most secure servers you can run. The tailscale propaganda is crazy in this community.

      source
• Manifish_Destiny@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Not for people who are asking questions about port forwarding

  source
• IphtashuFitz@lemmy.world ⁨1⁩ ⁨week⁩ ago

  If you have ssh open to the world then it’s better to disable root logins entirely and also disable passwords, relying on ssh keys instead.

  source
• piccolo@ani.social ⁨1⁩ ⁨week⁩ ago

  I dont expose ssh to the internet. I expose wireguard. If you want ssh youll have to break my wiregaurd key and my ssh key.

  source
• Trainguyrom@reddthat.com ⁨1⁩ ⁨week⁩ ago

  For public facing only use key based authentication. Passwords have too much risk associated for public facing ssh

  source