22 on a remote server? Also considering the fact that the password is long randomly generated (disabled password authentication as well) + using SSH keys?
you should be ok, as long as you are using modern keys for key auth
Cool, ssh-ed25519 is what I am using right now. Just that some people keep suggesting me to block port 22 and use some non-standard port for SSH saying it's not secure and I should avoid port 22, so wanted a second opinion as to how secure it actually is for the way I do things (only SSH keys based authentication enabled)
there is no reason to just change ssh port really, aside from a really dumb port-scanners. Attacker is one nmap scan from getting your ssh port anyways. Disabling 22 port and enabling port-knocking is the right way to do that.
Yes kinda
Обсуждают сегодня