Comment on Do I Need to Harden SSH over Tor?

• marcos@lemmy.world ⁨2⁩ ⁨months⁩ ago

  This is the internet. If you poke the bear, somebody will come-up with a completely reasonable use case of password authentication that happened once somewhere on the world.

  source

  • thebardingreen@lemmy.starlightkel.xyz ⁨2⁩ ⁨months⁩ ago

    Easy. I have servers that are only available on my local network and lots of different devices that I MIGHT want to use to access those servers. I haven’t bothered to make sure my key is on EVERY SINGLE DEVICE and some of them, I might not actually even WANT my key on as they’re not terribly well secured and they might leave my house (my Windows gaming laptop I haven’t used in six months comes to mind).

    But for cloud accessible servers… yeah.

    source

    • EarMaster@lemmy.world ⁨2⁩ ⁨months⁩ ago

      You know you’re allowed (some might even say supposed) to have different keys for different machines. They’re basically free to generate and take up to no space.

      source

      • lud@lemm.ee ⁨2⁩ ⁨months⁩ ago

        I use a different key for every device I need to connect to.

        So my phone has separate keys for each SSH server and so does my desktop and laptop.

        It’s not the most convenient thing in the world but it’s not too bad.

        Most of the keys are without passphrase but the keys I use to connect to my VPS for example absolutely have a passphrase.

        source
  • captain_aggravated@sh.itjust.works ⁨2⁩ ⁨months⁩ ago

    Playing with a Raspberry Pi inside my own home network with nothing important going on and I turned the Pi off when I’m done. Like why worry about it at that point?

    source

    • Acters@lemmy.world ⁨2⁩ ⁨months⁩ ago

      Yes, but I usually add my public key to the authorized_keys file and turn off password authentication once i do login with a password. On top of that, I have a sshpass one line command that takes care of this for me. It’s much easier than trying to manually type a password for the next time. I save it and just run it every time I think about using password login. Next time I need to ssh, I know the password login is not necessary.

      sshpass -p ‘PASSWORD’ ssh USER@IP.ADDRESS “echo ‘cat ~/.ssh/id_rsa.pub’ > ~/.ssh/authorized_keys && echo ‘Match User !root PasswordAuthentication no Match all’ > /etc/ssh/sshd_config’ && exit” && ssh USER@IP.ADDRESS

      At the next reboot, your system will now only accept key logins, except for root. I hope the root user password is secure. I don’t require it for root because if a hacker does gain shell access, a password(or priv esc exploit) is all they need to gain root shell. It is also a safety net in case you need to login and lost your private key.

      source
    • marcos@lemmy.world ⁨2⁩ ⁨months⁩ ago

      Yeah, that’s not a good reason.

      It’s much easier to authorize a key than to input your password on every kind of interaction.

      source
  • AbidanYre@lemmy.world ⁨2⁩ ⁨months⁩ ago

    If the is, I’d love to hear it. But even JuiceSSH on Android has supported keys for like the last decade.

    source
• someonesmall@lemmy.ml ⁨2⁩ ⁨months⁩ ago

  30 character password + fail2ban after one failed attempt. Why not?

  source

  • AbidanYre@lemmy.world ⁨2⁩ ⁨months⁩ ago

    WCGW?

    source

    • someonesmall@lemmy.ml ⁨2⁩ ⁨months⁩ ago

      Tell me

      source

      • chaospatterns@lemmy.world ⁨2⁩ ⁨months⁩ ago

        Accidentally typo your password and get blocked. And if you’re tunneling over tor, you’ve blocked 127.0.0.1 which means now nobody can login.

        source

        • -> View More Comments
  • wreckedcarzz@lemmy.world ⁨2⁩ ⁨months⁩ ago

    30 character

    You’ve gotta pump those numbers, those are rookie numbers. (I have a vps that has several times that figure)

    source

    • someonesmall@lemmy.ml ⁨2⁩ ⁨months⁩ ago

      Did you read my message? After one failed attempt you will get banned.

      source

      • wreckedcarzz@lemmy.world ⁨2⁩ ⁨months⁩ ago

        But

        30 characters

        :P

        source