fuzz: target for iprep data files
This should probably be mixed with rules (and pcap?) so that the files are picked by the detect engine.
A simpler way would be to directly expose the parsing routines, but I think getting the detect engine set up and packets eval'd will cover quite a bit more.
Updated by Philippe Antoine almost 2 years ago
prep stands for IP reputation cf reputation.c
I think this ticket should be covered with the similar ones : #3587 to #3590
There are all additional configuration files
We can try to fuzz them with structure awareness or not.
Structure awareness may be especially useful for the files parsed by PCRE
Anyways I think a good seed corpus with valid versions of all files should be relevant there.
So, we want one target that combines all these and checks them against some traffic.
But here, we want to focus fuzzing on the use of these configuration files.
So maybe, we should be selective where we instrument fuzzing coverage...