Valid reason: Testing something that uses ssh, but the test host already has a sshd running on port 22, and one does not want to disrupt that setup for the tes

Valid reason: Testing something that uses ssh, but the test host already has a sshd running on port 22, and one does not want to disrupt that setup for the test. Or running tests as a local, non admin, user and one does not want to bother the admin with modifying the system sshd setup for those tests. Other reasons: Those doing it /instead/ of running on port 22 are usually doing it for one of at least two reasons: 1) a false sense of security. If you do an internet search, you'll find plenty of blog posts boasting that using an alternate port is a security feature (it is not, it is security via obscurity); or 2) to reduce the log growth from all the script kiddie scans that target port 22 (note, no security is added here, but one's log files don't grow quite as rapidly either).