<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>fail2ban on {bjørn:johansen}</title>
    <link>https://bjornjohansen.com/tag/fail2ban/</link>
    <description>Recent content in fail2ban on {bjørn:johansen}</description>
    <generator>Hugo -- 0.118.2</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 07 Nov 2014 19:31:38 +0000</lastBuildDate>
    <atom:link href="https://bjornjohansen.com/tag/fail2ban/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using fail2ban to block WordPress login attacks</title>
      <link>https://bjornjohansen.com/using-fail2ban-with-wordpress/</link>
      <pubDate>Fri, 07 Nov 2014 19:31:38 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:35333461-3535-5165-a134-373366663038</guid> 
      <description>Fail2ban works by filtering a log file with a regular expression triggering a &lt;code&gt;ban&lt;/code&gt; action if the condition is met. After a preset time, it will trigger an &lt;code&gt;unban&lt;/code&gt; action. Without much effort, we can have WordPress log all authentication events and have fail2ban react on them.</description>
    </item>
    <item>
      <title>Using fail2ban from behind a Rackspace Cloud LoadBalancer</title>
      <link>https://bjornjohansen.com/fail2ban-rackspace-loadbalancer/</link>
      <pubDate>Fri, 07 Nov 2014 19:31:31 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:34343362-6565-5331-b461-373762623161</guid> 
      <description>If your fail2ban is on a host behind a Rackspace Cloud LoadBalancer, you’ll want to block the offending IP addresses directly in your LoadBalancer. If your LB is acting as a reverse proxy, you’ll HAVE to block in the LB, but it is also nice to protect all other nodes behind the LB and offload the lifting.</description>
    </item>
  </channel>
</rss>
