diff options
author | van Hauser <vh@thc.org> | 2021-01-14 14:15:01 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-01-14 14:15:01 +0100 |
commit | c42875ddea1e5cb8da9a292b0fba19d0c69b09e5 (patch) | |
tree | 72936eff6d3e9242b7a880109a2f811e83a7c570 /docs | |
parent | 68acd3d101b8407abf7e3a55bd2cf9b3b694534b (diff) | |
parent | 53c7aaa57bf5473c5d6a4553c0178410fef17cbc (diff) | |
download | afl++-c42875ddea1e5cb8da9a292b0fba19d0c69b09e5.tar.gz |
Merge pull request #688 from murx-/dev
Update documentation to reflect new default power schedule
Diffstat (limited to 'docs')
-rw-r--r-- | docs/power_schedules.md | 4 | ||||
-rw-r--r-- | docs/status_screen.md | 7 |
2 files changed, 8 insertions, 3 deletions
diff --git a/docs/power_schedules.md b/docs/power_schedules.md index 06fefa12..493f9609 100644 --- a/docs/power_schedules.md +++ b/docs/power_schedules.md @@ -13,8 +13,8 @@ We find that AFL's exploitation-based constant schedule assigns **too much energ | AFL flag | Power Schedule | | ------------- | -------------------------- | -| `-p explore` (default)|  | -| `-p fast` | =\\min\\left(\\frac{\\alpha(i)}{\\beta}\\cdot\\frac{2^{s(i)}}{f(i)},M\\right)) | +| `-p explore` |  | +| `-p fast` (default)| =\\min\\left(\\frac{\\alpha(i)}{\\beta}\\cdot\\frac{2^{s(i)}}{f(i)},M\\right)) | | `-p coe` |  | | `-p quad` |  | | `-p lin` |  | diff --git a/docs/status_screen.md b/docs/status_screen.md index 0cede6ff..0329d960 100644 --- a/docs/status_screen.md +++ b/docs/status_screen.md @@ -29,13 +29,18 @@ With that out of the way, let's talk about what's actually on the screen... ### The status bar +``` +american fuzzy lop ++3.01a (default) [fast] {0} +``` + The top line shows you which mode afl-fuzz is running in (normal: "american fuzy lop", crash exploration mode: "peruvian rabbit mode") and the version of afl++. Next to the version is the banner, which, if not set with -T by hand, will either show the binary name being fuzzed, or the -M/-S main/secondary name for parallel fuzzing. -Finally, the last item is the power schedule mode being run (default: explore). +Second to last is the power schedule mode being run (default: fast). +Finally, the last item is the CPU id. ### Process timing |