Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removal of severity from blocking rules leads to CrowdSec hiccoughs when running CRS4 #3607

Open
dune73 opened this issue Mar 9, 2024 · 2 comments
Labels
🐛 bug Something isn't working

Comments

@dune73
Copy link
Member

dune73 commented Mar 9, 2024

See coreruleset/modsecurity-crs-docker#215 for bug report and discussion.

@dune73 dune73 added the 🐛 bug Something isn't working label Mar 9, 2024
@theseion
Copy link
Contributor

theseion commented Mar 9, 2024

I wonder whether we should really change this in core. To me it makes sense that we dropped the severity action. Maybe add a plugin for CrowdSec that makes CrowdSec work?

@dune73
Copy link
Member Author

dune73 commented Mar 11, 2024

I see little need to change CRS and having CrowdSec users install a plugin is kind of annoying.

So I think CrowdSec should update. But leaving this open so we can track the situation.

@theseion theseion changed the title Removal of severity from blocking rules leads to CrowdSec hiccups when runnning CRS4 Removal of severity from blocking rules leads to CrowdSec hiccoughs when running CRS4 Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants