> You can maintain a .ssh/config file with all the port that you used (and backup it)
Once you start distributing config files to all your clients you might as well switch to keypair authentication, which so completely reduces risk of intrusion that leaving sshd on 22 simply does not matter.
Once you start distributing config files to all your clients you might as well switch to keypair authentication, which so completely reduces risk of intrusion that leaving sshd on 22 simply does not matter.
> that consumes resources (even if minimal)
I suspect practically immeasurable.