diff options
| author | van Hauser <vh@thc.org> | 2019-06-07 21:32:27 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-07 21:32:27 +0200 |
| commit | 46e58b434acf66181bc64f82c754d3294e15bd3e (patch) | |
| tree | d38a333f941d112da6f2854534fd735d90645146 /docs | |
| parent | ba37bf13d60dd6d889d7125d996412f99651ef07 (diff) | |
| parent | 263fd37590e0326ea9b6f91924caf3db266fc855 (diff) | |
| download | afl++-46e58b434acf66181bc64f82c754d3294e15bd3e.tar.gz | |
Merge pull request #4 from practicalswift/typo
Fix typos
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/perf_tips.txt | 2 | ||||
| -rw-r--r-- | docs/power_schedules.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/perf_tips.txt b/docs/perf_tips.txt index 287284fc..263065c0 100644 --- a/docs/perf_tips.txt +++ b/docs/perf_tips.txt @@ -191,7 +191,7 @@ There are several OS-level factors that may affect fuzzing speed: - Use the afl-system-config script to set all proc/sys settings above - Disable all the spectre, meltdown etc. security countermeasures in the - kernel if your machine is properly seperated: + kernel if your machine is properly separated: "ibpb=off ibrs=off kpti=off l1tf=off mds=off mitigations=off no_stf_barrier noibpb noibrs nopcid nopti nospec_store_bypass_disable nospectre_v1 nospectre_v2 pcid=off pti=off spec_store_bypass_disable=off diff --git a/docs/power_schedules.txt b/docs/power_schedules.txt index 578ff020..cb4ca6e7 100644 --- a/docs/power_schedules.txt +++ b/docs/power_schedules.txt @@ -27,7 +27,7 @@ where *α(i)* is the performance score that AFL uses to compute for the seed inp More details can be found in our paper that was recently accepted at the [23rd ACM Conference on Computer and Communications Security (CCS'16)](https://www.sigsac.org/ccs/CCS2016/accepted-papers/). -PS: In parallel mode (several instances with shared queue), we suggest to run the master using the exploit schedule (-p exploit) and the slaves with a combination of cut-off-exponential (-p coe), exponential (-p fast; default), and explore (-p explore) schedules. In single mode, the default settings will do. **EDIT:** In parallel mode, AFLFast seems to perform poorly because the path probability estimates are incorrect for the imported seeds. Pull requests to fix this issue by syncing the estimates accross instances are appreciated :) +PS: In parallel mode (several instances with shared queue), we suggest to run the master using the exploit schedule (-p exploit) and the slaves with a combination of cut-off-exponential (-p coe), exponential (-p fast; default), and explore (-p explore) schedules. In single mode, the default settings will do. **EDIT:** In parallel mode, AFLFast seems to perform poorly because the path probability estimates are incorrect for the imported seeds. Pull requests to fix this issue by syncing the estimates across instances are appreciated :) Copyright 2013, 2014, 2015, 2016 Google Inc. All rights reserved. Released under terms and conditions of Apache License, Version 2.0. |