diff options
| -rw-r--r-- | docs/ideas.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ideas.md b/docs/ideas.md index 92b3ce49..10d97ca0 100644 --- a/docs/ideas.md +++ b/docs/ideas.md @@ -4,16 +4,16 @@ In the following, we describe a variety of ideas that could be implemented for f ## Flexible Grammar Mutator -Currently, AFL++'s mutation do not have deeper knowledge about the fuzzed binary, apart from feedback, even though the developer may have insights about the target. A developer may chose to provide dictionaries and implement own mutations in python or c, but an easy mutator that behaves according to a given grammar, does not exist. +Currently, AFL++'s mutation does not have deeper knowledge about the fuzzed binary, apart from feedback, even though the developer may have insights about the target. A developer may choose to provide dictionaries and implement own mutations in python or c, but an easy mutator that behaves according to a given grammar, does not exist. ## LTO Based Non-Colliding Edge Coverage -An unsolved problem in fuzzing, right now, are hash collisions between paths. By iterating through all functions at link time, assigning unique values to each branch, therefore reducing or even eliminating collisions, should be possible. +An unsolved problem in our fuzzing, right now, are hash collisions between paths. By iterating through all functions at link time, assigning unique values to each branch, therefore reducing or even eliminating collisions, should be possible. ## QEMU 4-based Instrumentation First tests to use QEMU 4 for binary-only AFL++ showed that caching behavior changed, which vastly decreases fuzzing speeds. -This is the case why, right now, we cannot switch to QEMU 4.2. Understanding the current instumentation and fixing the current caching issues will be needed. +This is the cause why, right now, we cannot switch to QEMU 4.2. Understanding the current instrumentation and fixing the current caching issues will be needed. ## WASM Instrumentation |