News for hackers. Stuff that matters.
Re:Practical Linux Hardening Guide by noja on Thursday January 24, 2019 @05:24PM (#18993653)
Better to have it listening on a port below 1024, otherwise a non-root user could impersonate the ssh daemon.
Re:Practical Linux Hardening Guide by noir_lord on Thursday January 24, 2019 @05:59PM (#18993931)
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.
Re:Practical Linux Hardening Guide by noja on Friday January 25, 2019 @05:34PM (#19003257)
A non-root user might not be a person, it might be a compromised php script.
Re:Practical Linux Hardening Guide by noir_lord on Saturday January 26, 2019 @05:32AM (#19005726)
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.)
Re:Practical Linux Hardening Guide by noja on Friday January 25, 2019 @05:35PM (#19003263)
A lot of people who don't care much for checking keys.