about summary refs log tree commit diff
path: root/utils
diff options
context:
space:
mode:
Diffstat (limited to 'utils')
-rw-r--r--utils/argv_fuzzing/README.md4
-rw-r--r--utils/libdislocator/README.md8
-rw-r--r--utils/libtokencap/README.md2
3 files changed, 7 insertions, 7 deletions
diff --git a/utils/argv_fuzzing/README.md b/utils/argv_fuzzing/README.md
index 192d72f7..e9224995 100644
--- a/utils/argv_fuzzing/README.md
+++ b/utils/argv_fuzzing/README.md
@@ -1,6 +1,6 @@
 # argvfuzz
 
-AFL supports fuzzing file inputs or stdin. When source is available,
+AFL++ supports fuzzing file inputs or stdin. When source is available,
 `argv-fuzz-inl.h` can be used to change `main()` to build argv from stdin.
 
 `argvfuzz` tries to provide the same functionality for binaries. When loaded
@@ -13,4 +13,4 @@ A few conditions need to be fulfilled for this mechanism to work correctly:
 2. If the target binary does not use the default libc's `_start` implementation
    (crt1.o), the hook may not run.
 3. The hook will replace argv with pointers to `.data` of `argvfuzz.so`. If the
-   target binary expects argv to be living on the stack, things may go wrong.
+   target binary expects argv to be living on the stack, things may go wrong.
\ No newline at end of file
diff --git a/utils/libdislocator/README.md b/utils/libdislocator/README.md
index d0340af0..64a5f14c 100644
--- a/utils/libdislocator/README.md
+++ b/utils/libdislocator/README.md
@@ -28,7 +28,7 @@ heap-related security bugs in several ways:
 
   - Optionally, in platforms supporting it, huge pages can be used by passing
     USEHUGEPAGE=1 to make.
-  
+
   - Size alignment to `max_align_t` can be enforced with AFL_ALIGNED_ALLOC=1.
     In this case, a tail canary is inserted in the padding bytes at the end
     of the allocated zone. This reduce the ability of libdislocator to detect
@@ -49,7 +49,7 @@ The allocator is slow and memory-intensive (even the tiniest allocation uses up
 for "production" uses; but it can be faster and more hassle-free than ASAN / MSAN
 when fuzzing small, self-contained binaries.
 
-To use this library, run AFL like so:
+To use this library, run AFL++ like so:
 
 ```
 AFL_PRELOAD=/path/to/libdislocator.so ./afl-fuzz [...other params...]
@@ -62,7 +62,7 @@ Similarly to afl-tmin, the library is not "proprietary" and can be used with
 other fuzzers or testing tools without the need for any code tweaks. It does not
 require AFL-instrumented binaries to work.
 
-Note that the AFL_PRELOAD approach (which AFL internally maps to LD_PRELOAD or
+Note that the AFL_PRELOAD approach (which AFL++ internally maps to LD_PRELOAD or
 DYLD_INSERT_LIBRARIES, depending on the OS) works only if the target binary is
 dynamically linked. Otherwise, attempting to use the library will have no
-effect.
+effect.
\ No newline at end of file
diff --git a/utils/libtokencap/README.md b/utils/libtokencap/README.md
index 91ebebd1..343fcce0 100644
--- a/utils/libtokencap/README.md
+++ b/utils/libtokencap/README.md
@@ -43,7 +43,7 @@ when using afl-gcc. This setting specifically adds the following flags:
 The next step is to load this library via LD_PRELOAD. The optimal usage pattern
 is to allow afl-fuzz to fuzz normally for a while and build up a corpus, and
 then fire off the target binary, with libtokencap.so loaded, on every file found
-by AFL in that earlier run. This demonstrates the basic principle:
+by AFL++ in that earlier run. This demonstrates the basic principle:
 
 ```
   export AFL_TOKEN_FILE=$PWD/temp_output.txt