owasp-modsecurity / owasp-modsecurity/ModSecurity
Support macro expansion on ruleRemoveTargetById/ctl
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Adds macro expansion on ruleRemoveTargetById/ctl target.
More information on Macro expansion: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#Macro_Expansion
References:
- https://github.com/SpiderLabs/ModSecurity/blob/27dd513ab656d15f87acf6d2b81e32f5d0082465/apache2/re.c#L2604-L2629
- https://github.com/SpiderLabs/ModSecurity/blob/27dd513ab656d15f87acf6d2b81e32f5d0082465/apache2/re.c#L55-L149
- https://github.com/SpiderLabs/ModSecurity/blob/master/apache2/re_actions.c#L1221-L1237
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the referenced apache2/re.c ranges and apache2/re_actions.c, then trace how ruleRemoveTargetById and ruleRemoveTargetById/ctl targets are handled in the current tree. Compare that handling with the referenced macro-expansion paths. Done means macro expansion is supported for these targets and the relevant behavior is covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100