4 ms·
You can maintain a .ssh/config file with all the port that you used (and backup it) or use always the same custom port. Anyway, it is useless but it can avoid
by alerighi 4y ago
You can maintain a .ssh/config file with all the port that you used (and backup it) or use always the same custom port.
Anyway, it is useless but it can avoid all sort of bots trying out common login to your SSH server, that consumes resources (even if minimal) and fills your logs.
- anjbe 4y ago> 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. > that consumes resources (even if minimal) I suspect practically immeasurable.
- amelius 4y agoHow do you pick a good port number that doesn't clash now and in the future? Ps: it is a disgrace that the network/kernel still uses port numbers rather than names, which would be much more flexible.