Fail2Ban VS neovim

something like https://github.com/renanqts/xdpdropper or cilium's host firewall or https://github.com/boylegu/TyrShield exist or https://github.com/ebpf-security/xdp-firewall today and implement ebpf filter based firewalling.

Of these there is a sample integration for XDPDropper to fail2ban that never got merged https://github.com/fail2ban/fail2ban/pull/3555/files -- I don't think anyone else has really worked on that junction of functionality yet.

There's also wazuh which seems to package ebpf tooling up with a ton of detection and management components, but its not a simple to deploy as fail2ban.

Fail2Ban: Stop brute-force attacks

Wasn't that the argument against https, namely, that it was too costly to run [1]? I also run fail2ban [2] in my servers and I rarely even notice it's there.

I'm not saying you should sit down with the iptables manual and start going through the logs, but I can see the idea taking off if all it takes is (say) one apt-get and two config lines.

[1] https://stackoverflow.com/questions/1035283/will-it-ever-be-...

[2] https://github.com/fail2ban/fail2ban

Not a whole lot of a source to share, sorry.

Whenever registering/subscribing to some provider, I always use a new,unique email address. If/when that provider gets their user database leaked, after some time, spam starts rushing in. At that point, I change my email address in provider's records, and old one is moved to "spamtrap" alias on my server. Over the years, quite a few has accumulated - linkedin, yahoo, you name it...

Fail2ban [0] parses mail server logs, and I have a rule there, where source IP address of anything incoming to spamtrap, is looked up in whois and logged. Then, manual awk/grep/sort contraption is run periodically.

DO's AS14061 used to be consistently in top-3 spam sources, occasionally taking #1 spot.

[0] http://www.fail2ban.org/

IP Ban: Fail2ban

First you need to install Fail2ban. Before installation please see official installation guide on GitHub. Maybe something has been changed after this article published.

Throughout this I'll be referring to these pages: https://nixos.wiki/wiki/Fail2ban https://github.com/dani-garcia/vaultwarden/wiki/Fail2Ban-Setup https://github.com/fail2ban/fail2ban/blob/master/config/action.d/cloudflare.conf

Impatient of what exactly? fail2ban is battle tested for well over a decade. It is also an active project with regular updates: https://github.com/fail2ban/fail2ban/commits/master/

now some things you need to think about: - cloud init - this will need to be secure so lock it down hard anything not needed an alternative OS to look at if you have the ability's is https://www.alpinelinux.org/ also as these devices are not that powerfull every extra agent / abstaction layer you add impacts performance need to look at low over head security https://www.crowdsec.net/ and https://github.com/fail2ban/fail2ban (if you call fail2ban security) - using certificates to authenticate ssh login

Neovim

Vim is a highly efficient, keyboard-driven text editor that prioritizes speed, precision, and control. It’s been around for decades, but it’s far from outdated. In recent years, Vim has seen a resurgence, thanks largely to Neovim, a modern refactor of Vim that brings a faster core, better plugin support, and a vibrant, forward-looking community.

A text-based shell interface is extremely lightweight compared to modern IDEs. Because it runs in the terminal, even a feature-rich agent has very low overhead. According to Forgecode “Low Resource Usage: minimal impact on system performance”. In contrast, a full IDE can consume hundreds of megabytes of RAM or more, even when idle. In one user benchmark, Neovim (a terminal editor) used only about 10 MB of RAM, whereas Visual Studio Code (an Electron-based IDE) used roughly 700 MB with no files open. The savings add up quickly: even a hundred developers using shell agents could free up many gigabytes of memory compared to the same number running heavy IDE instances. In practice, a shell agent like Forge leaves almost all CPU and RAM free for your code compilation and tests. In a cloud or CI/CD pipeline, this efficiency translates directly into cost savings. You can run more parallel analyses or smaller instances when the tools are light. Over time, those saved resources mean lower infrastructure bills for large teams.

So I headed over to the Neovim GitHub like any lost soul would and followed the official install steps:

Neovim GitHub Repository

PDE (Personalized Development Environment): Neovim

I've used VSCode for years. It's great, no doubt. But when you have to juggle up to 5 projects daily, you'll find that it's going to block you away. Mine feels heavy, especially with multiple windows and extensions. This is why I decided to find an alternative, until I started using NeoVim instead.