From b517e02cda49e378e4656e2d8690e4ffd4d17ed2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20Sz=C3=A9pe?= Date: Tue, 11 Jul 2017 14:46:02 +0200 Subject: [PATCH] https://github.com/fail2ban/fail2ban/issues/1156 --- ...hosting-where-Fail2ban-is-not-available.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Ban-IP-s-on-shared-hosting-where-Fail2ban-is-not-available.md diff --git a/Ban-IP-s-on-shared-hosting-where-Fail2ban-is-not-available.md b/Ban-IP-s-on-shared-hosting-where-Fail2ban-is-not-available.md new file mode 100644 index 0000000..2b1c460 --- /dev/null +++ b/Ban-IP-s-on-shared-hosting-where-Fail2ban-is-not-available.md @@ -0,0 +1,22 @@ +I am missing fail2ban so much on cheap shared hosting that I've _rewritten_ it in PHP. + +### Actions + +There are several kinds of banning (I call them methods, not actions) + +- Apache RewriteMap + RewriteRule [F] +- Apache SetEnvIf + Deny +- CloudFlare API +- Respond with HTTP 403 (and no further banning) +- Nginx user config (TODO) +- Tarpit (and no further banning) +- WordPress plugin based + +See https://github.com/szepeviktor/wordpress-fail2ban/tree/master/miniban + +### Features + +- whitelist +- ban time +- unban +- etc.