-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Implement support for ctl:ruleRemove family of actions in libModSecurity #1607
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
Comments
Some actions of ctl:ruleRemove are already implemented: rule_remove_by_id, SecRuleRemoveByID and SecRuleRemoveByMsg have also been implemented on v3 already. You can follow the progress at #1476. |
Hi, this issue seems to be present still: service nginx restartPerforming sanity check on nginx configuration: Config for the location: Running 3.0.0 on nginx 1.12.2 on FreeBSD (we're the port maintainers for 3.0 on FreeBSD) |
To be clear - SecRuleRemoveById works as expected in this context. |
It's easter vacation around here, haven't got time to update the port and rebuild. Expect to be able to test properly next week.
Thanks,
/Eirik
|
I've used these heavily in my 2.x CRS implementation. With modsecurity and CRS 3.x upgrade I'd like to know whether to port my rules without using these directives or wait for the implementation.
The text was updated successfully, but these errors were encountered: