LibAFL icon indicating copy to clipboard operation
LibAFL copied to clipboard

Clean up and document fuzzers directory

Open domenukk opened this issue 3 years ago • 6 comments

Currently, ./fuzzers is full of very similar fuzzers with hardly any differences. Also, it may not be clear what the differences are to the untrained eye. We should clean this up and document it.

Also, fuzzers like frida_libpng should be made more general (i.e.: not build libpng in build.rs)

domenukk avatar Dec 16 '21 01:12 domenukk

I am new to fuzzing and I went through the LibAFL docs and now going through all the modules and sub-modules. I can clean up and document each fuzzer as I learn about that modules used in each fuzzer.

highonweb avatar Dec 28 '21 16:12 highonweb

i want to contribute in this section

debrajrout avatar Mar 10 '22 06:03 debrajrout

Is it OK to add description of different fuzzers(like baby_fuzzer_gramatron or baby_fuzzer_tokens) in docs/src?

syheliel avatar Mar 10 '22 11:03 syheliel

docs/src is about the libafl book and I agree babyfuzzer's description should go there. but for others I think a single and improved README.md is enough(?)

cc @domenukk

tokatoka avatar Mar 11 '22 15:03 tokatoka

I have added some description for baby_fuzzer_* in #564

syheliel avatar Mar 12 '22 05:03 syheliel

Hey @tokatoka I am interested in working on this issue. I am a student developer from IIT BHU keen to contribute to AFL++.

shubhangi013 avatar Feb 28 '23 21:02 shubhangi013