Better to have it listening on a port below 1024, otherwise a non-root user could impersonate the ssh daemon.
I agree except if a non-root user I don't know about is binding to any ports from inside then I'm already hosed.
A non-root user might not be a person, it might be a compromised php script.
True but if my system has a compromised anything binding to a port then they can talk to it via whatever they want at that point.
I'm of the opinion that if an attacker gets a local account then I'm already hosed given the regularity of local privilege escalation CVE's
Re:Practical Linux Hardening Guide
by deathanatos on Thursday January 24, 2019 @07:10PM
(#18994341)
This would be detected by SSH, as the host key wouldn't match. (The impersonator wouldn't be able to use the same host key, as they would need the private key, and that requires root privs.)
A lot of people who don't care much for checking keys.
Re:Practical Linux Hardening Guide
by ASalazarMX on Thursday January 24, 2019 @05:18PM
(#18993615)
Conveniency through obscurity.
Yep, which is far better than 'security' through obscurity.
I'm so sorry, but my OCD could not let this pass. It's "convenience" not "conveniency". Sorry.
EDITED TO ADD: I wholeheartedly agree with the sentiment though.
It stopped my logs from getting splattered with failed attempts.