-
Notifications
You must be signed in to change notification settings - Fork 24
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
Support generative fuzzers #6
Comments
This includes: Add option "type": "gen"/"mut" to fuzzer definitions: Handle the type in fuzzingiterationdata::fuzzData(). If "gen":
Remove hardcodet checks to load pickle file if selected fuzzer is "gen":
Do the same also for honggmode in |
- Readme.md : Linked the grammar based fuzzer tutorial - docs/tutorial-grammar-based.md : Added the grammar based fuzzer tutorial for Dharma - fuzzer/fuzzer_list.py : Created a py file to have the fuzzer list there (easy config) - fuzzer/fuzzingiterationdata.py : Changes for issue 6 - fuzzer/fuzzingmaster.py : Changes for issue 6 - fuzzer/fuzzingslave.py : Changes for issue 6 - template/fuzzing.py : Added the grammars file to fuzzing.py
The first idea, as depicted here and implemented in 1bd4393 was not a good idea. 4e9e5b3 fixes it partially. I just created a fake network message structure (data.pickle) in fuzzingmaster.py. This has the advantage that most of the other code can stay the same (for gen/mut fuzzers). Open tasks:
(1) Usability is the wrong word, but the user currently has no way of specifying when the generated data is sent. Should FFW read first, and then sent the generated data, or the other way round? Should message nummero 8 be replaced with some generated XML? All this is not possible atm. |
Note: Fenrir broke generative fuzzers, i think. I'll either remove it completely, or re-active it later. |
Currently FFW only supports mutation fuzzers, which are based on prerecorded data from the interceptor.
It should also support generative fuzzers, which do not have prerecorded data.
The text was updated successfully, but these errors were encountered: