diff options
| author | van Hauser <vh@thc.org> | 2022-03-17 16:30:29 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-17 16:30:29 +0100 |
| commit | 1bea949f34fb437a60ca772787a9018a3ba79053 (patch) | |
| tree | 59d6f7ef2222cb92835d08398de3a1d32d2f8528 /docs/fuzzing_binary-only_targets.md | |
| parent | 3c11a377570512efeb3a197148ff1b7dddbd8e32 (diff) | |
| parent | 1a65df2beee0a68bd5198a44f42ae1346f7ee231 (diff) | |
| download | afl++-1bea949f34fb437a60ca772787a9018a3ba79053.tar.gz | |
Merge branch 'dev' into newpm2
Diffstat (limited to 'docs/fuzzing_binary-only_targets.md')
| -rw-r--r-- | docs/fuzzing_binary-only_targets.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/fuzzing_binary-only_targets.md b/docs/fuzzing_binary-only_targets.md index 1a2b27c7..c97af1b9 100644 --- a/docs/fuzzing_binary-only_targets.md +++ b/docs/fuzzing_binary-only_targets.md @@ -48,11 +48,12 @@ The following setup to use QEMU mode is recommended: Then run as many instances as you have cores left with either -Q mode or - even better - use a binary rewriter like Dyninst, RetroWrite, ZAFL, etc. +The binary rewriters all have their own advantages and caveats. +ZAFL is the best but cannot be used in a business/commercial context. -If [afl-dyninst](https://github.com/vanhauser-thc/afl-dyninst) works for your -binary, then you can use afl-fuzz normally and it will have twice the speed -compared to QEMU mode (but slower than QEMU persistent mode). Note that several -other binary rewriters exist, all with their advantages and caveats. +If a binary rewriter works for your target then you can use afl-fuzz normally +and it will have twice the speed compared to QEMU mode (but slower than QEMU +persistent mode). The speed decrease of QEMU mode is at about 50%. However, various options exist to increase the speed: |