Optimization #3587
openfuzz: target for threshold.config
Added by Victor Julien about 6 years ago. Updated 7 months ago.
VJ Updated by Victor Julien about 6 years ago Actions #1
- Priority changed from Normal to Low
VJ Updated by Victor Julien about 6 years ago Actions #2
- Assignee set to Philippe Antoine
PA Updated by Philippe Antoine about 5 years ago Actions #3
- Related to Task #4125: tracking: Better fuzzing added
PA Updated by Philippe Antoine over 4 years ago Actions #4
Should this target use rules and traffic as well ?
There does not seem to be much to fuzz in SCThresholdConfParseFile by itself
VJ Updated by Victor Julien over 4 years ago Actions #5
Rules for sure, yes, as the threshold rules are applied to regular rules. Of course coverage may get higher with traffic, although I could imagine that reaching the thresholding conditions from traffic+rules might be tricky. But maybe I'm underestimating the fuzz algos.
VJ Updated by Victor Julien over 4 years ago Actions #6
Since the threshold file has rules that reference the regular rules by sig_id, I wonder if there should be some logic in the fuzz target to make sure we don't get a billion inputs that never reference a rule.
PA Updated by Philippe Antoine over 4 years ago Actions #7
I could imagine that reaching the thresholding conditions from traffic+rules might be tricky
Would not fuzzer set the threshold to 2 to easily reach it ?
Since the threshold file has rules that reference the regular rules by sig_id,
Indeed, see my comment in https://redmine.openinfosecfoundation.org/issues/3589#note-5
PA Updated by Philippe Antoine almost 3 years ago Actions #8
- Target version set to QA
PA Updated by Philippe Antoine over 1 year ago Actions #9
- Label Hardening added
PA Updated by Philippe Antoine 7 months ago Actions #10
- Status changed from New to Assigned