<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Crowdsec - Tag - vo.rs</title><link>https://vo.rs/tags/crowdsec/</link><description>Crowdsec - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 02 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/crowdsec/" rel="self" type="application/rss+xml"/><item><title>Locking Out the Bots: Fail2ban and CrowdSec on a Modern Linux Server</title><link>https://vo.rs/story/locking-out-the-bots-fail2ban-and-crowdsec/</link><description>&lt;p&gt;Stand up a server, give it a public IP address, and within minutes complete strangers will start trying to log in. They are not people; they are tireless scripts sweeping the entire internet, guessing usernames and passwords, probing for known vulnerabilities, and hammering login forms in the hope that one in a million lands. Your authentication logs fill with failed attempts from places you have never been. This background radiation of automated attacks is simply the weather of the modern internet, and the question is not whether you will be probed but how cheaply you can make the probing fail. Two tools dominate the answer: the venerable Fail2ban and the newer, crowd-sourced CrowdSec. This guide covers both, and how they fit together.&lt;/p&gt;</description><pubDate>Sat, 02 May 2026 10:00:00 +0000</pubDate></item></channel></rss>