there is such a utility GitHub - mitchellkrogza/nginx-ultimate-bad-bot-blocker: Nginx Block Bad Bots, Spam Referrer Blocker, Vulnerability Scanners, User-Agents, Malware, Adware, Ransomware, Malicious Sites, with anti-DDOS, Wordpress Theme Detector Blocking and Fail2Ban Jail for Repeat Offenders
what from this list can crowdsec block?
Is it possible that something that cannot block can be screwed into crowdsec?
Hi and thanks for the question.
In terms of what CrowdSec can block compared to the bad bot blocker there’s some of it here: CrowdSec Hub. I’d advise you to search the gub to potentially find more.
Regarding your other question I don’t understand. Can you elaborate? It’s already now possible to create scenarios that doesn’t trigger an alert and hence doesn’t block anything. Is that what you’re looking for? If not please elaborate on what you’re looking to achieve. Check our docs: Format | CrowdSec and look for overflow_filter.
I’d recommend that you join our Discord for a faster reply going forward. Find it at CrowdSec.
I don’t speak English very well
the script above can block Nginx Bad Bot and User-Agent Blocker, Spam Referrer Blocker, Anti DDOS, Bad IP Blocker and Wordpress Theme Detector Blocker
as I understand crowdsec from this list can block by User-Agent and is some kind of Anti DDOS, and is a Bad IP blocker
but is not a Spam Referrer blocker, or is it?
I don’t really understand, crowdsec completely replaces the functionality of the utility above?