diff options
| author | Moshe Kaplan <me@moshekaplan.com> | 2021-07-20 15:59:40 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-20 15:59:40 -0400 |
| commit | 6a6387582c9a08af49c73e7a29bc85cca0c1a047 (patch) | |
| tree | c5770d1421a37b1a601387aa0589f72c78fa3eb7 | |
| parent | 32a0d6ac31554a47dca591f8978982758fb87677 (diff) | |
| download | afl++-6a6387582c9a08af49c73e7a29bc85cca0c1a047.tar.gz | |
Update README.persistent_mode.md
| -rw-r--r-- | instrumentation/README.persistent_mode.md | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/instrumentation/README.persistent_mode.md b/instrumentation/README.persistent_mode.md index 24f81ea0..26c7aa8f 100644 --- a/instrumentation/README.persistent_mode.md +++ b/instrumentation/README.persistent_mode.md @@ -2,13 +2,16 @@ ## 1) Introduction -The most effective way is to fuzz in persistent mode, as the speed can easily +In persistent mode, afl++ fuzzes a target multiple times +in a single process, instead of forking a new process for each fuzz execution. +This is the most effective way to fuzz, as the speed can easily be x10 or x20 times faster without any disadvanges. -*All professional fuzzing is using this mode.* +*All professional fuzzing uses this mode.* -This requires that the target can be called in a (or several) function(s), -and that its state can be resetted so that multiple calls can be performed -without resource leaks and former runs having no impact on following runs + +Persistent mode requires that the target can be called in one or more functions, +and that its state can be reset so that multiple calls can be performed +without resource leaks and earlier runs will have no impact on future runs (this can be seen by the `stability` indicator in the `afl-fuzz` UI). Examples can be found in [utils/persistent_mode](../utils/persistent_mode). |