I woke up this morning, went into the kitchen, collected some spoons1, it's time to roll up my sleeves and release #iocaine 3.1.
Drank 0.4l of caffeinated hot chocolate, and topped it with two pellets of Ferrero Pocket Coffee. So I'm like wide-eye awake for the next hour, and I'm hearing colours2. ↩︎
iocaine's soothing green is, as expected, soothing, like a small breeze upon a field of wild grass. My burning red-yellow rage is the most metal sound you ever heard. ↩︎
Dependencies and changelog updated,iocaine-3.x branch likewise. Tag & release, then I have to update the documentation.
Of course, my CI has to compile rustc and whatnot for some reason. So this'll take some time!
One of the major things coming to iocaine 3.2 is the ability to fiddle with nftables things. This will let you firewall IPs, subnets or even entire ASNs, right from iocaine's script.
The default handler will have an option to add IPs (or their ASN) that hit poisoned URLs to a deny list (with optional expiry, handled by nftables). This feature will be off by default.
I expect this will make it a whole lot easier to handle large crawler waves, there will be no need for fail2ban or bazmeg, iocaine will take care of it itself.
The downside is that this will be linux-only. I have no idea how to do the same thing under any of the BSDs.
