3 ms·
Really, this sounds like a bad practice to bind on non privileged port. A user can keep running a program to check if your non privileged port can be bound and
by h1d 8y ago
Really, this sounds like a bad practice to bind on non privileged port.
A user can keep running a program to check if your non privileged port can be bound and if it could, it can start any behaving daemon that could be pretending to be a valid SSH daemon but could have anything like key loggers. Even a single restart of sshd could make it happen.
- wiml 8y agoIt doesn't have access to the host keys, so it can't do very much unless you intentionally bypass the "someone is intercepting your connection" error your ssh client will give you in that case.