diff options
| -rw-r--r-- | docs/custom_mutators.md | 2 | ||||
| -rw-r--r-- | instrumentation/README.lto.md | 2 | ||||
| -rw-r--r-- | utils/autodict_ql/readme.md | 6 | ||||
| -rwxr-xr-x | utils/qbdi_mode/README.md | 6 |
4 files changed, 8 insertions, 8 deletions
diff --git a/docs/custom_mutators.md b/docs/custom_mutators.md index 3a2ec3b2..7d362950 100644 --- a/docs/custom_mutators.md +++ b/docs/custom_mutators.md @@ -218,7 +218,7 @@ trimmed input. Here's a quick API description: to the maximum amount of steps you returned in `init_trim`). Omitting any of three trimming methods will cause the trimming to be disabled -and trigger a fallback to the builtin default trimming routine. +and trigger a fallback to the built-in default trimming routine. ### Environment Variables diff --git a/instrumentation/README.lto.md b/instrumentation/README.lto.md index 24e57b23..b97e5799 100644 --- a/instrumentation/README.lto.md +++ b/instrumentation/README.lto.md @@ -328,7 +328,7 @@ and `CXXFLAGS=-flto=full`). If this succeeds, then there is an issue with afl-clang-lto. Please report at [https://github.com/AFLplusplus/AFLplusplus/issues/226](https://github.com/AFLplusplus/AFLplusplus/issues/226). -Even some targets where clang-12 fails can be build if the fail is just in +Even some targets where clang-12 fails can be built if the fail is just in `./configure`, see `Solving difficult targets` above. ## History diff --git a/utils/autodict_ql/readme.md b/utils/autodict_ql/readme.md index 9170f552..a28f1725 100644 --- a/utils/autodict_ql/readme.md +++ b/utils/autodict_ql/readme.md @@ -43,7 +43,7 @@ Do the following : # chmod +x codeql-build.sh # ./codeql-build.sh # source ~/.bashrc -# codeql +# codeql ``` Then you should get: @@ -84,12 +84,12 @@ Commands: - `python3 autodict-ql.py [CURRECT_DIR] [CODEQL_DATABASE_PATH] [TOKEN_PATH]` - example : `python3 /home/user/AFLplusplus/utils/autodict_ql/autodict-ql.py $PWD /home/user/libxml/libxml-db tokens` - This will create the final `tokens` dir for you and you are done, then pass the tokens path to AFL++'s `-x` flag. -5. Done! +5. Done! ## More on dictionaries and tokens Core developer of the AFL++ project Marc Heuse also developed a similar tool named `dict2file` which is a LLVM pass which can automatically extract useful tokens, in addition with LTO instrumentation mode, this dict2file is automatically generates token extraction. `Autodict-QL` plugin gives you scripting capability and you can do whatever you want to extract from the Codebase and it's up to you. In addition it's independent from LLVM system. -On the other hand, you can also use Google dictionaries which have been made public in May 2020, but the problem of using Google dictionaries is that they are limited to specific file formats and specifications. For example, for testing binutils and ELF file format or AVI in FFMPEG, there are no prebuilt dictionaries, so it is highly recommended to use `Autodict-QL` or `Dict2File` features to automatically generate dictionaries based on the target. +On the other hand, you can also use Google dictionaries which have been made public in May 2020, but the problem of using Google dictionaries is that they are limited to specific file formats and specifications. For example, for testing binutils and ELF file format or AVI in FFMPEG, there are no pre-built dictionaries, so it is highly recommended to use `Autodict-QL` or `Dict2File` features to automatically generate dictionaries based on the target. I've personally prefered to use `Autodict-QL` or `dict2file` rather than Google dictionaries or any other manually generated dictionaries as `Autodict-QL` and `dict2file` are working based on the target. In overall, fuzzing with dictionaries and well-generated tokens will give better results. diff --git a/utils/qbdi_mode/README.md b/utils/qbdi_mode/README.md index 2e8b01d4..cd59fb9c 100755 --- a/utils/qbdi_mode/README.md +++ b/utils/qbdi_mode/README.md @@ -34,9 +34,9 @@ For x86 standalone-toolchain ./build/tools/make_standalone_toolchain.py --arch x86 --api 21 --install-dir ../android-standalone-toolchain-x86 ``` -In alternative you can also use the prebuilt toolchain, in that case make sure +In alternative you can also use the pre-built toolchain, in that case make sure to set the proper CC and CXX environment variables because there are many -different compilers for each API version in the prebuilt toolchain. +different compilers for each API version in the pre-built toolchain. For example: @@ -129,7 +129,7 @@ int target_func(char *buf, int size) { } ``` -This could be build to `libdemo.so`. +This could be built to `libdemo.so`. Then we should load the library in template.cpp and find the `target` function address. ```c |