<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fail2ban on ads' corner</title><link>https://andreas.scherbaum.la/tags/fail2ban/</link><description>Recent content in Fail2ban on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 Dec 2022 17:21:00 +0100</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/fail2ban/index.xml" rel="self" type="application/rss+xml"/><item><title>Using fail2ban to block unfriendly web requests</title><link>https://andreas.scherbaum.la/post/2022-12-09_using-fail2ban-to-block-unfriendly-web-requests/</link><pubDate>Fri, 09 Dec 2022 17:21:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2022-12-09_using-fail2ban-to-block-unfriendly-web-requests/</guid><description>&lt;p&gt;Every time I peek into the webserver logfiles, I find quite a few 404 requests trying to figure out if certain exploits exist on this server. Now I get that these are automated attempts, and the number of requests coming from one IP show that they try several different exploits and path names. Nevertheless I thought that I don’t need this in my log, and on my webserver. &lt;a href="https://www.fail2ban.org/"&gt;fail2ban&lt;/a&gt; for the rescue.&lt;/p&gt;</description></item></channel></rss>