NethSecurity: Fail2ban/crowdsec/banip

[pike (Michael Kicks)]

With Crowdsec as a business partner I don’t see fail2ban interesting for the dev team.
And I would like to say that’s a bad idea.
What exposed here

Crowdsec the next fail2ban generation

It’s power… is also it’s weakness. This “db” crowd-created is “more rule” and so “more CPU power” used for retrieving, processing, checking and “let the buggers drop” when they try to connect. On the other side, missing login/knocks on the server could save CPU power, but it’s a lot of balancing. This might be useful for avoiding emerging botnets, well known buccaneers, but… buccaneers may be already available/stored into threatshield. Which is, in my humble opinion, the nice complement for F…

still stands

Edit: the bold part is inaccurate and it’s not true.
More on that here.
https://community.nethserver.org/t/nethsec8-ddclient/23415/6?u=pike