From fb76fd768f40751980cd444ad55907c1c315d8bf Mon Sep 17 00:00:00 2001 From: "Sergey G. Brester" Date: Sun, 13 Oct 2019 20:24:46 +0200 Subject: [PATCH] Updated Proper fail2ban configuration (markdown) --- Proper-fail2ban-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Proper-fail2ban-configuration.md b/Proper-fail2ban-configuration.md index 37ef61f..a5a5527 100644 --- a/Proper-fail2ban-configuration.md +++ b/Proper-fail2ban-configuration.md @@ -36,7 +36,7 @@ But value of parameter `logpath` in `section2` will be changed to `/my-path/to/l **[A]** You should create a `jail.local` file and at least enable there corresponding jails (all jails are disabled by default) resp. overwrite there all the settings you've different from normally stock installation, or even create your own jails (and/or) filters, that are not available in default configuration of the fail2ban distribution. -For example if you'll, that fail2ban should ban authorization failures occurred in sshd and nginx, but the `error.log` of your your nginx-instance is configured as `/var/log/my-nginx/error.log` you should set also parameter `logpath` additionally to `enabled` in section `[nginx]`. +For example if your intention is to monitor authorization failures occurred in sshd and nginx, but the `error.log` of your your nginx-instance is configured as `/var/log/my-nginx/error.log` you should set also parameter `logpath` additionally to `enabled` in section `[nginx]`. So your `jail.local` looks like: ```ini