diff options
| author | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-12-02 19:52:10 +0100 |
|---|---|---|
| committer | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-12-02 19:52:10 +0100 |
| commit | b7395fa46710673602b8fb7257e502e5f129a56c (patch) | |
| tree | c7ba9ea67e66d67b51d824413ec1ba87af72966b /docs/afl-fuzz_approach.md | |
| parent | 3023a36d4d2d2f4549d637bd505ba9ebd743788b (diff) | |
| download | afl++-b7395fa46710673602b8fb7257e502e5f129a56c.tar.gz | |
Change "AFL" to "AFL++"
Diffstat (limited to 'docs/afl-fuzz_approach.md')
| -rw-r--r-- | docs/afl-fuzz_approach.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/afl-fuzz_approach.md b/docs/afl-fuzz_approach.md index 4e8e5eaa..3e4faaec 100644 --- a/docs/afl-fuzz_approach.md +++ b/docs/afl-fuzz_approach.md @@ -348,7 +348,7 @@ That last bit is actually fairly interesting: it measures the consistency of observed traces. If a program always behaves the same for the same input data, it will earn a score of 100%. When the value is lower but still shown in purple, the fuzzing process is unlikely to be negatively affected. If it goes into red, -you may be in trouble, since AFL will have difficulty discerning between +you may be in trouble, since AFL++ will have difficulty discerning between meaningful and "phantom" effects of tweaking the input file. Now, most targets will just get a 100% score, but when you see lower figures, @@ -506,7 +506,7 @@ directory. This includes: - `edges_found` - how many edges have been found - `var_byte_count` - how many edges are non-deterministic - `afl_banner` - banner text (e.g. the target name) -- `afl_version` - the version of AFL used +- `afl_version` - the version of AFL++ used - `target_mode` - default, persistent, qemu, unicorn, non-instrumented - `command_line` - full command line used for the fuzzing session |