News for hackers. Stuff that matters.
Re:Practical Linux Hardening Guide by sliken on Thursday January 24, 2019 @07:04PM (#18994314)
Right, but say you have a dozen machines you login from regularly and maybe a few 100 that you login from occasionally. You want to maintain a ~/.ssh/config on all of them?

Seems like a big inconvenience for minimal extra security. Not like scanning for all open ports that have an ssh listening is hard.

Re:Practical Linux Hardening Guide by joppy on Thursday January 24, 2019 @07:25PM (#18994416)
If you’re already typing in the full address for the server every time, since you don’t have an ssh config file, then is it really so much more work to additionally type the port?
Re:Practical Linux Hardening Guide by mcny on Monday January 28, 2019 @05:46AM (#19016455)
Yes because I will forget to type -p 5223 at some point. If you set up a non standard port against my recommendation and I get banned for trying 22, you better be on call 24/7 for free to unban me.
Re:Practical Linux Hardening Guide by yjftsjthsd-h on Thursday January 24, 2019 @09:04PM (#18994930)
If you are coming from 100s of machines, I would really hope you have your home on NFS or something anyways.