From 2746607d870c2d09e7a697bf523ababdc4d088d9 Mon Sep 17 00:00:00 2001 From: "Sergey G. Brester" Date: Fri, 23 Aug 2019 09:44:28 +0200 Subject: [PATCH] Updated Best practice (markdown) --- Best-practice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Best-practice.md b/Best-practice.md index 68bed9b..f900ed2 100644 --- a/Best-practice.md +++ b/Best-practice.md @@ -7,7 +7,7 @@ Here are the advises and common smart practices in order to drive Fail2ban opera * If log-file or journal show several different types of messages or some pre-filtering may be advantageous, use common `prefregex` (and short and efficient as possible); * Reorganize the regex-order by occurrence in log (frequently as first). This is valid for all regex too. * Try to reduce count of log-messages (especially unneeded or unrelated information, which is called "parasitic" further) in observing log-file or journal. See section [Reduce parasitic log-traffic](#reduce-parasitic-log-traffic) below. -* Use incremental bantime (since v.0.11) as well as other Fail2Ban new features might help you to minimize intrusions count resp. to reduce attacks in the long perspective. +* Use incremental bantime (since v.0.11) as well as other Fail2Ban new features might help you to minimize intrusions attempt count resp. to reduce attacks in the long perspective. * Under DDOS-attack similar circumstances use other tools and make special arrangements too, may be in combination with Fail2Ban and/or information it could provide you. Please note, Fail2Ban is just a tool and it depends on what you make out of it. ### Reduce parasitic log-traffic