aboutsummaryrefslogtreecommitdiff
path: root/utils
diff options
context:
space:
mode:
Diffstat (limited to 'utils')
-rw-r--r--utils/afl_network_proxy/README.md13
-rw-r--r--utils/afl_untracer/README.md6
2 files changed, 10 insertions, 9 deletions
diff --git a/utils/afl_network_proxy/README.md b/utils/afl_network_proxy/README.md
index 05659c45..d2c00be2 100644
--- a/utils/afl_network_proxy/README.md
+++ b/utils/afl_network_proxy/README.md
@@ -34,16 +34,17 @@ afl-network-server -i 1111 -m 25M -t 1000 -- /bin/target -f @@
### on the (afl-fuzz) main node
-Just run afl-fuzz with your normal options, however the target should be
+Just run afl-fuzz with your normal options, however, the target should be
`afl-network-client` with the IP and PORT of the `afl-network-server` and
increase the -t value:
+
```
afl-fuzz -i in -o out -t 2000+ -- afl-network-client TARGET-IP 1111
```
-Note the '+' on the -t parameter value. The afl-network-server will take
-care of proper timeouts hence afl-fuzz should not. The '+' increases the
-timeout and the value itself should be 500-1000 higher than the one on
-afl-network-server.
+
+Note the '+' on the -t parameter value. The afl-network-server will take care of
+proper timeouts hence afl-fuzz should not. The '+' increases the timeout and the
+value itself should be 500-1000 higher than the one on afl-network-server.
### networking
@@ -53,7 +54,7 @@ either. Note that also the outgoing interface can be specified with a '%' for
Also make sure your default TCP window size is larger than your MAP_SIZE
(130kb is a good value).
-On Linux that is the middle value of `/proc/sys/net/ipv4/tcp_rmem`
+On Linux that is the middle value of `/proc/sys/net/ipv4/tcp_rmem`
## how to compile and install
diff --git a/utils/afl_untracer/README.md b/utils/afl_untracer/README.md
index ada0c916..9f41618f 100644
--- a/utils/afl_untracer/README.md
+++ b/utils/afl_untracer/README.md
@@ -5,9 +5,9 @@
afl-untracer is an example skeleton file which can easily be used to fuzz
a closed source library.
-It requires less memory and is x3-5 faster than qemu_mode however it is way
-more course grained and does not provide interesting features like compcov
-or cmplog.
+It requires less memory and is x3-5 faster than qemu_mode, however, it is way
+more course grained and does not provide interesting features like compcov or
+cmplog.
Supported is so far Intel (i386/x86_64) and AARCH64.