ziggy
ziggy copied to clipboard
srlabs
A multi-fuzzer management utility for all of your Rust fuzzing needs 🧑🎤
When ziggy builds his targets, the used folder is `$PWD/target`. When in a workspace, the `target` directory will be at the root of the workspace. This makes that we cannot...
automation: * If `cargo ziggy build` fails then send a notification * If `cargo ziggy run` fails then send a notification * If a crash is found, send a notification...
When using cargo ziggy add-seeds, we should also copy the seeds to shared_corpus
In this PR I'll add a third fuzzer to our roster: LibAFL. I'll start by making it very simple and include corpus sharing and basic monitoring. In the future, we...
AFL has the possibility to configure [partial instrumentation](https://github.com/AFLplusplus/AFLplusplus/blob/stable/instrumentation/README.instrument_list.md). This could help the fuzzer concentrate on the important part as well as have a coverage that is only on what we...
Not sure how this could look but: the issue is that we use ziggy on very special targets, hence our default setup is not ideal for other targets, e.g. text...
AFL++/LibAFL-type rabbit with Aladin Sane face paint. Thanks @brunoproduit for the idea!
See https://gist.github.com/louismerlin/437557264489797f530c6ba0caca27e3
stephan's idea: when doing `ziggy fuzz` also build a `coverage-worker` target that is compiled exactly the same as `coverage`. however for this one ziggy runs new inputs from afl/mainaflfuzzer/queue/id:* in...
We could have a subcommand that could create a dictionary file for the fuzzers, by doing some static analysis on: - a path that contains the code, through byte-value and...