Hello,
I have a few questions about configuring Fail2Ban:

1- The following options exist in two sections of Fail2Ban. One under [DEFAULT] section and another under the service configuration section:
Why?

2- If I set the value of findtime to 1d, that means the number of times that the wrong password is entered must happen during a day? For example, 3 times in one day.

3- What is the best value of findtime to avoid brute-force attack?

Thank you.

So that different services can have different configurations but if one isn't specified then the default will be used.
Pretty much. However 3 / 1d is crazy unless you've other mitigating factors to stop legitimate users getting locked out. Brute force attacks work by sending a lot of requests in rapid succession, so a smaller findtime is more appropriate.
Your favorite search engine should be your friend: https://www.linode.com/docs/guides/h...ce-protection/

1 members found this post helpful.

For what it's worth, I've found the default settings to be quite acceptable.

Hello,
Thank you so much for your reply.
If you define findtime = 10s and maxretry = 3, then the hacker enters the password twice under 10 seconds and enters the third time in 11 seconds, then will he\she be blocked?

Why would you want to have findtime set so crazy low? Remember there's "reaction time" involved here, which is the delay between sshd writing the failed attempt to the logs and Fail2Ban reading the logs. In general this will be low, but on a heavily loaded system there may be a reaction delay.

If you're looking to stop bad actors attempting to access / brute force your system, a bit of research, even reading your own log files would show that the typical attack vector is an attempt every few seconds. A typical pattern is also to try a single password and if that fails to "back off" for a few seconds then try again.

From experience I find the default values are sufficient to discourage automated attempts.

Hello,
Thanks again.
I think to prevent brute-force attack, findtime value should be 1s, but as you said, the best option is to look at the SSH logs to determine the best value.
How can I tell Fail2Ban to block an IP address if it enters the wrong password 3 times regardless of the time interval?

I believe it is bantime = -1. If you actually uses password only, then short findtime will ban your users often simply because they think they type in the wrong password and they will ask but you to unban them all the time. I find setting it to a few minutes suffices. Remember, this is for brute force /well known account and passwords. It is better to just use public keys auth, or integrate one time passwords using gauth or security devices. That way, no one has a "real" password.

So how do you know it's a brute-force attack if you're only looking at 1s? The signature of brute force is prolonged multiple password attempts. Many skript kiddy scripts will back off slight or attempt to randomize time between tries.
Depending on how your regular users interact with the system this isn't a particularly clever thing to do as it doesn't allow for things like regular user errors. Say I enter my password wrong because I used an old one, then enter the right one, then do the same thing a couple of times over the next few days, I'd get banned. Now maybe that's the behavior you want, but it will really annoy your regular users.

Hello,
Thank you so much for your reply.
1- So what settings do you recommend to protect against brute-force attacks?

2- I want to be blocked for one day if a person enters wrong password three times during the day. Is it possible?

You've already been told twice!
Post #3Post #5Yes.

Hi,
Thanks.
Can you tell me how can I block someone who has entered the wrong password three times in any given time period?

RTFM

These are the settings I use:
The person connecting gets 5 tries within 20 minutes. If they fail the 5 attempts, they start with a 20 minute ban. If they come back after the ban and fail again, the ban doubles, and will keep doubling after the failed attempts.

I also use a non-standard port so I'm not bombarded by bots.

I think in the years I've been running my server, only one person/bot was persistent enough to get a ban for several weeks before giving up.