5 ms·

Your .ssh/config can handle that for you?

• sliken 8y ago
  Sure, you could try to populate .ssh/config on every machine you ever will try to login from. Or you could use the standard port, turn off passwords, and wait for the sun to burn out before someone brute forces their way in.
  • amdavidson 8y ago
    Do you sync your ssh keys to all the machines you login from? How do you ssh-copy-id without some allowance for passworded logins? Especially if you're doing it from such distant machines that you can't scp over a .ssh/config file.
    • sliken 8y ago
      So, I just ssh to whatever machine I need to work on, but occasionally need to rsync or scp files to/from that server. Sure, I could have puppet push a ~/.ssh/config file everywhere, just seems more effort than it's worth. After all if a hacker wants to know if you are running ssh, it's not hard to scan all ports for ssh. Why inconvenience yourself more than the attacker?
  • romeisendcoming 8y ago
    Or someone can simply own your key holding device as you sip your beverage at the local hotspot or home wifi. Simpler to go after the secret privileged client than the server.