64
Thoughts on crowdsec (lemmy.ca)
submitted 2 months ago* (last edited 2 months ago) by to c/selfhosted@lemmy.world
27 comments fedilink hide all child comments
 

I have been running crowdsec on my OpenWRT firewall for a bit now, I am just curious as to what others think about it?

Thank you @irmadlad the webui you suggested is showing the logs a lot better than my vibe coded HA plug ins (both my ssh honey pot and my plug in showed nothing) looking over the logs shows so much activity that is happening.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 2 months ago (3 children)

How would it, or any software for that matter determine a given request is malicious before it does something malicious?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 months ago

    Crowdsec does it by using crowd-sourced blocklists (hence the name). So if an IP triggers a scenario on other machines, that malicious address will be proactively added to your blocklist before it ever gets a chance to impact your machine.

    That is the big advantage of crowdsec over reactive-only solutions, like fail2ban.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 2 months ago*

    Yes, that is the hard part. But it can be done. Geoip blocking like only allow your country - blocking every China or Russian user etc. If you are selfhosting at home and worry about your SSH access, then you can do a lot of things to block then early. It is all about authentication. Lets say you require VPN access in - example Wireguard. You could require access only through somebody else, like Cloud flare tunnel. You could also do "port knocking" but that is not encrypted. You could require the user first has to be authenticated somewhere else, like require first Microsoft login and only then your ip is allowed.

  • permalink
  • fedilink
  • source
  • parent