well.. nowadays, having 22 tcp exposed to WAN is not smart.. 
the first thing to do is to change sshd listening port to something > 1024..
in 15 years I had not a single line in the logs about ssh attacks (only failed logins, but it was me 
)
↧
Nethserver-fail2ban needs testers
↧