>Are you implying that DoS and brute force attacks are not real threats? Brute force should not be, we have key auth to prevent that. Use it. If you're using f

>Are you implying that DoS and brute force attacks are not real threats? Brute force should not be, we have key auth to prevent that. Use it. If you're using fail2ban to prevent DoS attacks you probably shouldn't be the person trying to prevent DoS attacks. >Is there another solution you prescribe to address these and related issues other than the solutions discussed in this thread, such as fail2ban, port fluxing, port knocking, and VPN? Key auth to stop brute forcing, VPN would be preferable to mitigate potential key compromise. >If you don't own and operate your own data center, which is becoming a rare thing these days, your servers are in a shared hosting environment. How do you define "shared hosting environment," and how is fail2ban "a little strange" unless in that context? "shared hosting" is a pretty clear term, and anyone who's dealt with hosting should know what it means. But in case you don't, it's almost always used to refer to setups where you've got multiple customers hosting their content on unprivileged accounts on a shared server. >What does root access (or the lack thereof) have to do with protecting daemons from network attacks? You need root for fail2bans SSH blocking to function.