diff options
| -rw-r--r-- | docs/custom_mutators.md | 4 | ||||
| -rw-r--r-- | docs/ideas.md | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/custom_mutators.md b/docs/custom_mutators.md index 2a77db82..0e94ab10 100644 --- a/docs/custom_mutators.md +++ b/docs/custom_mutators.md @@ -1,7 +1,7 @@ # Custom Mutators in AFL++ This file describes how you can implement custom mutations to be used in AFL. -For now, we support C/C++ library and Python module, collectivelly named as the +For now, we support C/C++ library and Python module, collectively named as the custom mutator. There is also experimental support for Rust in `custom_mutators/rust`. For @@ -272,7 +272,7 @@ For C/C++ mutators, the source code must be compiled as a shared object: gcc -shared -Wall -O3 example.c -o example.so ``` Note that if you specify multiple custom mutators, the corresponding functions -will be called in the order in which they are specified. e.g first +will be called in the order in which they are specified. e.g. first `post_process` function of `example_first.so` will be called and then that of `example_second.so`. diff --git a/docs/ideas.md b/docs/ideas.md index 1a578313..52b07c26 100644 --- a/docs/ideas.md +++ b/docs/ideas.md @@ -9,7 +9,7 @@ Currently analysis is done by using afl-plot, which is rather outdated. A GTK or browser tool to create run-time analysis based on fuzzer_stats, queue/id* information and plot_data that allows for zooming in and out, changing min/max display values etc. and doing that for a single run, different runs and -campaigns vs campaigns. Interesting values are execs, and execs/s, edges +campaigns vs. campaigns. Interesting values are execs, and execs/s, edges discovered (total, when each edge was discovered and which other fuzzer share finding that edge), test cases executed. It should be clickable which value is X and Y axis, zoom factor, log scaling on-off, etc. @@ -45,7 +45,7 @@ Mentor: vanhauser-thc Something with machine learning, better than [NEUZZ](https://github.com/dongdongshe/neuzz) :-) Either improve a single -mutator thorugh learning of many different bugs (a bug class) or gather deep +mutator through learning of many different bugs (a bug class) or gather deep insights about a single target beforehand (CFG, DFG, VFG, ...?) and improve performance for a single target. |