Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
fail2ban_add_custom_rule [06.12.2020 09:01] – Pascal Suter | fail2ban_add_custom_rule [06.12.2020 09:05] (current) – Pascal Suter | ||
---|---|---|---|
Line 4: | Line 4: | ||
usually your favorite distribution comes packed with filters and all you may have to do is enable them.. however, sometimes you might want to write your own rule, be it for your own application or for some case which is simply not covered by the default rules.. | usually your favorite distribution comes packed with filters and all you may have to do is enable them.. however, sometimes you might want to write your own rule, be it for your own application or for some case which is simply not covered by the default rules.. | ||
- | here is an example of how I added a new rule for postfix which filters out some bots who try to brute-force smtpd accounts. most of those are covered by the default filter in ubuntu, however, i had a case of a bot which tried to authenticate on a smtpd which only allowed TLS but it did not use TLS.. so the bot will honestly never suceed with this method of course, but it still was flooding my logs, so i decided to do something against that.. | + | here is an example of how I added a new rule for postfix |
+ | |||
+ | **NOTE** Please keep in mind, that path names and best practices on where to save your configs vary slightly from distribution to distribution.. debian and therefore ubuntu style is to not edit distribution provided config files and instead use the '' | ||
first let's look a the log entries which identify that sucker: | first let's look a the log entries which identify that sucker: |