HN

Comments (25)

• Menu

  mewse-hn
  Funny to see this after I spent the morning troubleshooting and fixing my crowdsec install on my debian 13 vps. Apparently they stopped supplying a community blocklist to my machine because I'm running the old debian packaged version instead of directly from them (http 500). I had a LLM build a blocklist from publicly available sources rather than tie myself more tightly to their SaaS platform.
• Menu

  sandeepkd
  On the funny side, reading the website tagline, apparently they claim to know who is attacking you, they just happen to miss out on who attacked them.Turns out they are not really a security company, just an aggregator of bad IPs. Ideally this kind of aggregator problem is best suited for a trusted not-for-profit company where providing the data needs some level of credibility and querying the data costs you nominal fee to keep the setup floating.
• giancarlostoro
  Sounds like an exploit took the credentials needed to extract the code, makes me wonder if a Ubikey + SSL cert for git access would have prevented the entire leak.
• Menu

  itintheory
  We implemented CrowdSec for bot/scraping mitigation. The architecture is sound, but it ended up having an unacceptable false positive rate for us. This may be an issue with any kind of IP reputation approach. After a couple of months of work getting it ready to go I had to turn it off after a couple of days.
• Menu

  sidcool
  Security firm hacked.
• xyst
  yet another security oriented company that doesn’t practice what they preach.On the flip side, there was allegedly no PII leaked. But this event is still a red flag as it means their internal ops are absolutely shit. So it’s another vendor receiving a PNG flag.CrowdSec. CrowdStrike.
• JonathanCross
  [flagged]
• laurennorthwood
  [flagged]
• gleezard
  [dead]