diff options
-rw-r--r-- | docs/env_variables.md | 4 | ||||
-rw-r--r-- | docs/fuzzing_in_depth.md | 6 | ||||
-rw-r--r-- | docs/important_changes.md | 10 |
3 files changed, 10 insertions, 10 deletions
diff --git a/docs/env_variables.md b/docs/env_variables.md index bb7ea70b..ec9b2b01 100644 --- a/docs/env_variables.md +++ b/docs/env_variables.md @@ -109,7 +109,7 @@ fairly broad use of environment variables instead: - `AFL_USE_MSAN=1` - activates the memory sanitizer (uninitialized memory) - `AFL_USE_TSAN=1` - activates the thread sanitizer to find thread race conditions - - `AFL_USE_UBSAN=1` - activates the undefined behaviour sanitizer + - `AFL_USE_UBSAN=1` - activates the undefined behavior sanitizer - `TMPDIR` is used by afl-as for temporary files; if this variable is not set, the tool defaults to /tmp. @@ -336,7 +336,7 @@ checks or alter some of the more exotic semantics of the tool: - Setting `AFL_DISABLE_TRIM` tells afl-fuzz not to trim test cases. This is usually a bad idea! - - `AFL_EXIT_ON_SEED_ISSUES` will restore the vanilla afl-fuzz behaviour which + - `AFL_EXIT_ON_SEED_ISSUES` will restore the vanilla afl-fuzz behavior which does not allow crashes or timeout seeds in the initial -i corpus. - `AFL_EXIT_ON_TIME` causes afl-fuzz to terminate if no new paths were found diff --git a/docs/fuzzing_in_depth.md b/docs/fuzzing_in_depth.md index c94590a4..8188a18e 100644 --- a/docs/fuzzing_in_depth.md +++ b/docs/fuzzing_in_depth.md @@ -178,8 +178,8 @@ The following sanitizers have built-in support in AFL++: * MSAN = Memory SANitizer, finds read access to uninitialized memory, eg. a local variable that is defined and read before it is even set. Enabled with `export AFL_USE_MSAN=1` before compiling. -* UBSAN = Undefined Behaviour SANitizer, finds instances where - by the C and - C++ standards - undefined behaviour happens, e.g. adding two signed integers +* UBSAN = Undefined Behavior SANitizer, finds instances where - by the C and C++ + standards - undefined behavior happens, e.g. adding two signed integers together where the result is larger than a signed integer can hold. Enabled with `export AFL_USE_UBSAN=1` before compiling. * CFISAN = Control Flow Integrity SANitizer, finds instances where the control @@ -196,7 +196,7 @@ The following sanitizers have built-in support in AFL++: of the target source code where you find a leak check necessary! Enabled with `export AFL_USE_LSAN=1` before compiling. -It is possible to further modify the behaviour of the sanitizers at run-time by +It is possible to further modify the behavior of the sanitizers at run-time by setting `ASAN_OPTIONS=...`, `LSAN_OPTIONS` etc. - the available parameters can be looked up in the sanitizer documentation of llvm/clang. afl-fuzz, however, requires some specific parameters important for fuzzing to be set. If you want diff --git a/docs/important_changes.md b/docs/important_changes.md index 877dfab2..9d6bbbbe 100644 --- a/docs/important_changes.md +++ b/docs/important_changes.md @@ -1,6 +1,6 @@ # Important changes in AFL++ -This document lists important changes in AFL++, for example, major behaviour changes. +This document lists important changes in AFL++, for example, major behavior changes. ## From version 3.00 onwards @@ -8,23 +8,23 @@ With AFL++ 3.13-3.20 we introduce frida_mode (-O) to have an alternative for binary-only fuzzing. It is slower than Qemu mode but works on MacOS, Android, iOS etc. -With AFL++ 3.15 we introduced the following changes from previous behaviours: +With AFL++ 3.15 we introduced the following changes from previous behaviors: * Also -M main mode does not do deterministic fuzzing by default anymore * afl-cmin and afl-showmap -Ci now descent into subdirectories like afl-fuzz -i does (but note that afl-cmin.bash does not) -With AFL++ 3.14 we introduced the following changes from previous behaviours: +With AFL++ 3.14 we introduced the following changes from previous behaviors: * afl-fuzz: deterministic fuzzing it not a default for -M main anymore * afl-cmin/afl-showmap -i now descends into subdirectories (afl-cmin.bash however does not) -With AFL++ 3.10 we introduced the following changes from previous behaviours: +With AFL++ 3.10 we introduced the following changes from previous behaviors: * The '+' feature of the '-t' option now means to auto-calculate the timeout with the value given being the maximum timeout. The original meaning of "skipping timeouts instead of abort" is now inherent to the -t option. With AFL++ 3.00 we introduced changes that break some previous AFL and AFL++ -behaviours and defaults: +behaviors and defaults: * There are no llvm_mode and gcc_plugin subdirectories anymore and there is only one compiler: afl-cc. All previous compilers now symlink to this one. All instrumentation source code is now in the `instrumentation/` folder. |