diff options
author | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-08-08 21:22:47 +0200 |
---|---|---|
committer | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-08-08 21:22:47 +0200 |
commit | ab43289c1a6232a308eeba9ed9b1a8fe8168f72d (patch) | |
tree | 873a5c822e7572c9146d4a4f24a832dc867838e5 /docs/parallel_fuzzing.md | |
parent | c779262d8924daa4ac2c127db2a699c818c3c709 (diff) | |
parent | df74625df0324e17178dbf3c7c03484719ef6dd0 (diff) | |
download | afl++-ab43289c1a6232a308eeba9ed9b1a8fe8168f72d.tar.gz |
Merge branch 'dev' into docs_edit_remote_monitoring
Diffstat (limited to 'docs/parallel_fuzzing.md')
-rw-r--r-- | docs/parallel_fuzzing.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/parallel_fuzzing.md b/docs/parallel_fuzzing.md index 23872899..90e12e89 100644 --- a/docs/parallel_fuzzing.md +++ b/docs/parallel_fuzzing.md @@ -27,7 +27,7 @@ will not be able to use that input to guide their work. To help with this problem, afl-fuzz offers a simple way to synchronize test cases on the fly. -Note that afl++ has AFLfast's power schedules implemented. +Note that AFL++ has AFLfast's power schedules implemented. It is therefore a good idea to use different power schedules if you run several instances in parallel. See [power_schedules.md](power_schedules.md) @@ -116,7 +116,7 @@ distribute the deterministic fuzzing across. Note that if you boot up fewer fuzzers than indicated by the second number passed to -M, you may end up with poor coverage. -## 4) Syncing with non-afl fuzzers or independant instances +## 4) Syncing with non-AFL fuzzers or independant instances A -M main node can be told with the `-F other_fuzzer_queue_directory` option to sync results from other fuzzers, e.g. libfuzzer or honggfuzz. |