WP fail2ban Blocklist

Àpèjúwe

There are many plugins that use a database to check for malicious IPs after they connect, and of course fail2ban stops repeated attacks, but what if bad IPs could be blocked before they attack?

By working collaboratively Ìtumọ̀ Yorùbá: – sharing attack data Ìtumọ̀ Yorùbá: – WP fail2ban Blocklist does exactly that.

The Blocklist Network Service (BNS) collects attack data from participating sites, performs some analytical magic, and sends back a list of IPs that are attacking sites now but havenÌtumọ̀ Yorùbá: ’t yet attacked that site. In other words, each site periodically gets a unique list of IPs to block preemptively.

GDPR

The BNS doesnÌtumọ̀ Yorùbá: ’t collect personal data, and bots donÌtumọ̀ Yorùbá: ’t have rights.

That said, the BNS only collects the minimum data required (time, IP, event), and only for IPs that have behaved maliciously.

Of course, it is possible that some data is generated by people behaving maliciously, but the BNS has no way to differentiate Ìtumọ̀ Yorùbá: – and nor should it: an attack is an attack.

Freemius

To work, the BNS must know:

• which sites are running the blocklist add-on,
• which version is in use,
• and a shared secret for secure communication.

Freemius already provides all these, and WP fail2ban already uses Freemius; why reinvent the wheel?

Therefore, unlike the core WP fail2ban plugin, you must opt into Freemius for the blocklist to work.